&-Contacting the author╥
Whats New?╥πPop Up Reference╡²PRM-data Menus Area▓╜Area Controls / Options Menuso2	Control Memory Useí&·Internal Protocol Options¢-5Dialing Options╨9∙Terminal Area Options╔=ôPort Select/Configure\F┤UART Line ControlS*Baud Select:Y7
Modem Connect Stringsqc¬Modem Response StringsgKModem Command Stringsfl~Default Video EmulationΣo{$Key Translation Sequence file (.KTS)_uⁿKeyboard MACRO Assignments[x>Directories in Use MenuÖâ╕Auto Engage Sequence TriggersQîG)"Intelligent Auto Log On Technology" (Tm)ÿ₧.EMSI/IEMSI data╞«┌Receiver Protocolsá┐mSender Protocols
┘ Telephone Directory Area∞Fon.Record Edit Menu"²δFile List/Utility Area
(Point Mail Functions5.┬Auto Answer Setups≈F5Event Schedules,K_"Mondo Menus" (Tm)ïNaMOUSE∞]jMacro LanguageVc╡	Macros list (LUI_)m%Macros list (Character I/O Functions)!é-Macros list (File Functions)NÄÑ%Macros list (Data Transfer functions)≤ö6&Macros list (Modem/Dialing/Fon.Record))Ñ└Macros list (Misc Functions)Θ│6(Macros list (Expandable PRM-data Macros)┐Σ	(Macros list (Expandable Macro Functions)╔╒Scripts - AutoScriptGen (Tm)╪╦Å!AceComm Registrationgφ╦
Order Form2±9Aboutk«

You can get more help by contacting the
author Michael Phelps at the following

- VOICE 602-846-4563 6 days 12-7pm MST

- BBS   602-846-2940 24 hours

- COMPUSERVE User ID 75120,3306

- FIDONET ADDRESS 1:114/35

- FIDONET ACECOMM ECHO
I distribute the "ACECOMM" echo to
USA NODES, until it makes BACKBONE.

- Write to: AceComm Software Support
            3003 North Central Ave
            Suite 121-171
            Phoenix, AZ  85012  USA


=============================================================
11/01/93 * Release version 1.75
=============================================================
Updates made for 1.75 include
  This release contains all the new functions I plan to put
  into AceComm other than minor suggestions, and tweaks. The
  script language, Auto Answer, and point mail services will
  get the most attention here after. The Windows version will
  be put on the front burner with the 1.75 release. (the
  Windows version is considered an upgrade for you registered
  users, I'm anxious to get this out)

- Re-written dialer
- Re-written script processor, the script language inches along,
  whats there is very solid
- Re-written log file formatter, nice new packed log file
- Part re-write for Dir Lister function, "Drives" detect works
  better, "NewDir" operates easier
  format also tracks online time
- Intelligent File Rename (internal zmodem)
- Itroduce "Mondo Menus" (Tm)
- New on-line help topics menu, supports scrollable view, and
   printing
- Changed TopBar 1 line menu for mouse to pull down menu type
  for most frequentl used commands. Hot key displayed at left
  Also displays current event schedule (if any) at right
- Changed status bar diplays "key-def" hot key & "help" menu
  hot keys at right
- Changed xstatus line display when creating or running scripts
   to display more clearly what key press options are allowed
- New Event scheduler for "Host", and "Mail" events
- New Intelligent Auto Answer (process macro stack associated
  with connect string), allows drop to BBS, FAX, etc. based on
  modem Answer/Connect string
- Re-written Point Mail
- New *.FLO file support (mailer) can look into MAIL_OUT
  directory and provide automated mail poll, send, attach, file
  request etc. if the current event scheduale allows. Manual
  mail functions still inside "Protocols" menus
- New Fon List menu item "Mass Change" any record item, updates
  all records with just the 1 item.
- A few new macros, [DATA_ARGS]
- DPRM175.EXE can clone the ACE.PRM file to ACE.CTL, your next
  upgrade will be painless


=============================================================
09/05/93 * Release version 1.7
=============================================================
Updates made for 1.7 include
- Introduces "Intelligent Auto Log On Technology"(Tm)
- Labels, Gotos, Ifs, and data areas are documented in example
  script file, and introduction of SCRIPT.DOC.
- Sorting FON files by system name, total calls, last date called
    and phone number.
- FON file import/convert functions will now allow file merging.
    US BBS list is a stable format, I'm converting that now.
- Internal protocols code to detect receive buffer near full was
    commented out, I un-commented it, slower computers running
    AceComm as a back ground in Windows etc don't see a crc error
    every 'buffer_size' bytes.
- Ansi ESC[6n is responded to with ESC[row;col R
- Extended AVATAR scroll up/scroll down functions
- File requests using FBL's nodelist extract files (.NOD) where
    the dir lister got involved, caused AceComm to create ACE.BCH
    instead of NETNODE.REQ, this problem didn't exist for users
    using the NODELIST.
- A memory management system has been implemented. Memory for
    internal functions can be swapped to XMS memory during other
    memory hungary tasks.  At this point AceComm uses 64k XMS for
    swapping the scroll back buffer.  Future releases will see
    EMS support, and much more high memory used for the scroll
    back buffer and reading very large FON files.  64k isn't
    much, it allows an extra 48k/250 FON record buffer for very
    large FON files.  Or With smaller FON files, AceComm can run
    in up to 64k less conventional memory than before.
    AceComm uses EMS/XMS/DISK for SWAP when using <CommandShell_>
    and <RunProgram> macros.
- Options menus have been re-arranged grouping like options into
    sub menus.
- LISTFILE names have been changed from ACE.BCH and temporary
    filenames of the 'ABCDEFG' order to 'UPLDS.LST' and
    'UPLDS.LS(n)'.
- Time slices for DV have been added.  Time slices for Windows
   are more selective. By default time slices are not given up
   while using any of Acecomm's internal protocols. Options for
   giving up time slices during internal protocols are provided
   in the new "Internal Protocols Options" menu.
- 9.6k memory has been freed due to changes in the help system
   and on line order form.


o The AceComm keyboard is macro driven

o The Popup Reference displays each key press that has been
  assigned to a MACRO, or MACROS.

o Current .KBD file is displayed, AceComm supports unlimited
  .KBD files. Current .KBD filename is always displayed at the
  right side of the Terminal Area's status line.

AceComm's Keyboard is re definable. Each key press can be re
assigned a different function, or set of functions. To
accomplish keyboard re definition, AceComm uses descriptive
text symbols called MACROS. MACROS are enclosed inside of
angled brackets.

The Pop Up Reference menu displays the current .KBD file's
MACRO(S) assignments.  A .KBD file contains a copy of all
key-press MACRO(S) assignments.  AceComm supports unlimited .KBD
files.  Each key press combination can be assigned a MACRO(S).
AceComm allows the user to re define the keyboard functions if so
desired.  AceComm provides a rich set of MACRO functions for all
of AceComm's internal functions.  A complete MACRO list with
descriptions is contained in the MACRO.DOC file.

- PgDn or <CR> will display the next key set at top of screen.

- Display  toggles the display from a text description and
  the actual macro assignments

  The key press is displayed to the left, with it's MACRO
  assignment to the right.  The example below shows the MACRO for
  AceComm's configurations area is assigned to ALT-P.

     ALT-P <PrmDataMenus_>              <= MACRO assign
     ALT-P Configuration Area           <= descriptive text

- Template allows you to print a list of keys that have MACRO
  assignments.  The default filename is "PRN".  You may find it
  handy to print to a FILE, (key.prn) or similar, this way you
  can format the TEMPLATE, for a more custom print job.


o MACRO for this menu is: <PrmDataMenus_>
  (default assignment is to both ALT O & ALT P)

o All PRM-data changes are auto-saved when Auto-Save flag is
  "ON" (default)

o Each sub-menu contains context sensitive HELP

Virtually any data contained inside the ACE.PRM file is
accessible and configurational from the PRM-data area.  Above is
the menu you will see after pressing key-combo <PrmDataMenus_> is
assigned to from the TERMINAL area.

Note: If you toggle "AutoSave" to Off, you will select the "Save
      Changes" option before exiting AceComm, if you want the
      toggled option to remain toggled.  Otherwise, AceComm will
      be back to "AutoSave" when re-started.


o The controls are enable/disable flags, some of which can
  also contain a value for timers.

o Sub menus contain more categorized controls


Most controls are a series of flags which tell AceComm when to
use some of the features, and when not to.  Flags with the ON/OFF
status are toggles, and will be toggled here in this menu.
Notice the "Screen Saver" flag description contains the number 5,
rather than an ON/OFF.  Selecting Screen Saver mode 0 = OFF.

- Allow enhanced keyboard detection        Yes
  AceComm will detect and use enhanced BIOS keyboard functions.
  Some systems may not fully support this mode properly. This
  flag allows locking out AceComm's use of enhanced BIOS
  keyboard functions.

- Allow mouse detection                    Yes
  Setting this to "NO" will cause AceComm to act as if a mouse
  is non existent, the mouse driver is never initialized, no
  mouse menu is presented in the Terminal Area.


- Mouse horizontal sensitivity             6
  Mouse sensitivity is already set in the mouse driver. This
  value is internal to AceComm only

- Mouse vertical sensitivity               4
  Mouse sensitivity is already set in the mouse driver. This
  value is internal to AceComm only

- Auto Save Changes                        On
  When "ON" AceComm will save PRM-data changes to the ACE.PRM
  file.  When "OFF" the prompt inside the main PRM-data menu must
  be selected for PRM-data changes to be recorded to file.  This
  pertains to actual PRM-data below the menu system data.  Menu
  area attributes are ALWAYS SAVED, with exception to "Mass Menu
  Area" changes, these must be affected using the appropriate
  selection from inside "Mass Menu".

- Screen Saver timeout value (minutes)     5
  Screen Blanking function.
  Screen Saver can be set from 0 - 10.  Values above 0 are
  minutes without a key press to AceComm blanking the screen.
  Screen is restored with a key press.  Un-blank-key-press is
  valid.  Use ALT alone for non-destructive key press to un-blank
  the screen.
  See also "Screen Saver if Data Carrier Detect" from Terminal
  Area Options menu.

- Keep Log file                            On
  Toggle AceComm use logging ON/OFF.

- All Sounds Override Switch <> Sounds are Off
  Toggle, enable/disable all sounds. Master override.



o With version 1.7, AceComm begins managing memory usage.

o AceComm can swap the scroll back buffer memory to XMS prior
  to allocating large chunks of memory for other operations.

o EMS will be supported in the next release.

o XMS and EMS are supported for the SWAP functions.

- XMS (kb) ok to use
  AceComm's internal memory manager can save overall memory
  requirements by swapping some internal data to XMS memory when
  about to perform another memory hungary task.

- Scroll Back (kb) to use
  Up to 64 kb (64 x 1024) memory can be used for the back
  buffer.
  Future versions of AceComm will begin allowing multiple
  64 kb memory be used for scroll back buffer.
  The first 64 kb memory is conventional memory.

- Swap for <RunProgram>                    On
  XMS, EMS, DISK swapping for the AceComm executable will take
  place when this flag is set "ON".  When SWAPPING is active,
  AceComm 's SIO is deactivated while <RunProgram> MACRO is
  active.
  Notes: AceComm is currently using Ralf Brown's SWAP functions
         for the SWAP service.  SWAP is the only code inside
         AceComm executable that is not written entirely by MGP
         Programming Services.  SWAP has proven to be the most
         dependable code of this type that has been tested in our
         executable files.  MGP Programming Services would like
         to thank Ralf Brown for permission to use his SWAP code
         in our products.

- Swap for <CommandShell_>              On
  XMS, EMS, DISK swapping for the AceComm executable will take
  place when this flag is set "ON".  When SWAPPING is active,
  AceComm 's SIO is deactivated while <CommandShell_> MACRO is
  active.
  Notes: The Notes for <RunProgram> apply to this MACRO



- Auto Engage                              Yes
  Activate/deactivate AutoD sequence triggers & Associated AutoM
  MACROS.

- File Rename                              Yes
  For internal Zmodem.  Rename "Yes" existing files when last
  modification time/date don't match.  AceComm will create a new
  filename. When file times don't match, we can assume that
  although the filenames are the same, they were created at
  different times, and probably contain different data.

  Example:
          The file "114-35.QWK" exists in our receive directory.
          The incoming filename is "114-35.QWK" also. AceComm's
          internal zmodem will then compare file times and if
          they match, it is safely these files are the same and
          a file size check is done to see if we can resume the
          download.
          If the file times don't match, AceComm's internal
          zmodem will try and create a filename "114-35.QW0",
          if this filename exists, "114-35.QW1" etc.
          Thus we can have several *same* filenames in our
          receive directory without overwriting them.
  Example:
          You download the "allfiles.lst" from the same BBS
          every week. The filename is always the same, the
          file times differ. AceComm will name duplicates names
          as "allfiles.lst", "allfiles.ls0", "allfiles.ls1" etc.

- File Resume                              Yes
  For internal Zmodem. Resume "Yes" existing files, data is
  appended to the file, "OFF", the file is created new, any
  existing file of the same name is over written. *If* the file
  modification time matched. Otherwise with File Rename
  function would have created it's unique filename.

  Example:
          You started down loading a file and were interrupted
          for some reason aborting the download. You log back
          on at a later time, and using Acecomm's internal zmodem
          begin to download the file once again. AceComm's
          internal zmodem will see if the file times match, and
          considers the to be the same file. Internal zmodem
          will tell the host zmodem to begin sending from the
          position where the file was aborted from. The file
          can be "Resumed", thus saving the time involved in
          down loading the entire file all over again.

- Ring bell after internal protocol        3
  Internal protocols will sound an alarm before returning to
  Terminal Area.  A value of "0" disables any sound after
  internal protocols.  A value of "1" plays a Victory tune.
  Values from 2-30 become seconds to sound the internal bell.
  See also <RingBell> 5 MACRO

- Time release from protocol               No
  Time slices for Windows/ OS/2, DV, and DOS are supported.
  This flag applies to the DV and DOS time releases.
  Releasing time to Windows/ OS/2 using the interrupt 2fh
  function causes so many missed interrupts that AceComm
  never releases int 2fh time slices during an internal
  protocol function.
  Time slices are otherwise given up generously.



- Inter Byte Delay                         1
  Add (value x 55 millisecond) delay between modem command
  characters.  With a value of '0' modem command strings are sent
  just as fast as the UART's Transmit Hold Register is Empty
  (THRE).  (I've observed Supra modems behave much better using a
  value of 1 for inter byte delay when in continuous re-dial)

- Modem Response Timeout when dialing      60
  Master timeout when dialing.  Overrides your modem's own S7
  register.
  Notes: It may be best to set this value several seconds above
         your modem's S7 register.

- Seconds between re dials                 1
  AceComm will pause this many seconds between receiving a modem
  response string, or timing out, and sending the next dial
  string to the modem.  The variable can be toggled from 0
  seconds to 90 seconds.

- Ring BELL on Dial/Connect                1
  Seconds to ring BELL on successful detection of either DCD or a
  connect message response from the modem.



- Status line                              On
  Toggle AceComm 's STATUS LINE On/Off
  Notes: AutoScrGen (Tm) will assert the STATUS LINE, and restore
         it on when through.  The RunScript function will do the
         same.

- Mouse Menu                              Yes
  Display 1 line mouse menu on Terminal Area screen

- Screen Saver if Data Carrier Detect      No
  Screen Blanking service disabled during modem status DCD bit
  detected to be ASSERTED.

- Terminal Area screen color (TTY mode)    7
  This setting allows changing the Terminal Screen color that is
  initially active when AceComm is started.  The color will
  remain constant through TTY video emulation.

- Drop DTR when quitting AceComm            No
  AceComm will or will not drop DTR when the <EndACECOMM> [n]
  MACRO is run.  Most modems will by default, drop carrier along
  with a drop in DTR.  DTR is a bit in the modem control register
  of the UART.  Setting this to "YES" will cause AceComm to drop
  DTR when ever <EndACECOMM> [n] MACRO is executed.

- Log modem response while off line        No
  AceComm can log modem response strings that come in.  This flag
  will tells AceComm if it should log the responses.  This is for
  off line only.  This flag is most use full when you want to
  know when your phone rings, AceComm will TIME STAMP PRM-data
  Area MDM_RESPONSE_RING responses strings.  Many modem ROMS are
  now featuring caller ID.  Modems that have caller ID ability
  will be able to present to the terminal screen the caller ID
  info, if available.  This information will also be logged along
  with the TIME STAMPED "RING".

- Strip high bit from incoming             Off
  "Off" data received from the modem is un altered. "ON" data
  is stripped of any bits above the decimal value 128.

- Default Video Emulation                  Av/An
  This selection brings up another menu.  The menu displays the
  available video terminal emulation modes.  Along with their
  associated KTS files.  This setting affects the default video
  terminal setting for AceComm.  Individual FON RECORDS contain
  their own video terminal settings.



Port numbers are merely symbolic for identification.  Port
addresses and the Interrupt ReQuest line for the address is
configurational.

- Install option, AceComm will close the active port and install
  it's SIO on the port selected.  MDM_INIT string is sent to
  modem.

- Edit option, you will be prompted for port address and IRQ.
  Address is a HEX number.  Entering a decimal value will fail.

- Rbuf/Tbuf are the buffer size used for serial I/O.  Normally
  there won't be any advantage to raising the TBuf size.  RBuf
  size will be adequate at about 1024 bytes for all normal use.
  The larger value (default) will allow storage of incoming
  during Back buffer, Tagger etc.  RBuf range is from 1k to 32k,
  TBuf 128 bytes to 32k.  The Zmodem sending unit's window size
  is equal to TBuf size.  Window size is not data-frame size.
  Window size means "how much data do we let build up into the TX
  buffer at any one time.  RBuf/TBuf can be changed at any time,
  on line or not.  It is recommended that the HOST be still when
  re-sizing RBuf/TBuf.  RBuf/TBuf changes take immediate affect.

- FIFO trigger is the number of bytes buffered before a First In
  First Out UART chip will alert the CPU by way of interrupt.
  FIFO UART operation is automatically enabled when a FIFO UART
  is detected.  AceComm always checks for FIFO UART presence
  whenever installing onto a PORT.  FIFO trigger level changes
  take immediate affect.  Trigger level of "1" affectively
  disables the FIFO affect.

- Chain IRQ "share IRQ" will cause AceComm 's SIO ISR to pass on
  the interrupt request to the Interrupt Service Routine which
  was present on the IRQ when AceComm installed onto the port.
  The Chain IRQ toggle takes immediate affect.  IRQ sharing is
  not supported by -most- I/O cards.  Use the option at your own
  risk.  Notes: IRQ sharing may appear to work properly on your
  setup, even though your hardware was not designed for IRQ
  sharing to take place.  There are some good technical points to
  be made for degradation that may be caused in the I/O cards,
  when forced to drive the IRQ line HIGH, while another is doing
  it's best to pull the same IRQ line LOW.

- TX is a flag that tells AceComm to use interrupt driven
  output.  Interrupt driven input is always on.  The TX toggle
  takes immediate affect.  If you FAST computer/modem setup is
  capable of overwhelming the other end when sending data,
  toggling TX "OFF" may improve the situation.

- CTS/RTS hardware handshaking / FLOW control Hardware
  handshaking may normally be left ON (default).  High speed
  modems using fast data rates and typically locked port rates
  will require software to use FLOW control.

- XON/XOFF software handshaking / FLOW control Many HOST software
  will recognize XON/XOFF FLOW control.  You may need software
  handshaking enabled for proper FLOW control while performing
  ascii uploads.

      Notes: AceComm uses FLOW control flags (above) primarily to
             detect when not to send data to the modem.

             AceComm will automatically use both forms of FLOW
             control when it detects the receive buffer getting
             full.


The UART's line control register can be set for several different
data arrangements.  Most common being 8 data bits, no parity bit,
1 stop bit.  Most BBS systems will use the 8N1 configuration.
The UART uses the line control information when assembling
incoming bits into a byte.  Setting this information from the
PRM-data area, the format is stored in the default settings for
AceComm to use.  When you look at the FON directory records you
will see that each record stores it's personal line control
setting to be used when dialing the record.  Data format is saved
with each individual record in the record's .FON file.  When
using AceComm in HOST mode the default setting will be used.
AceComm retains the default line control register setting in the
ACE.PRM file.  FON record line control settings are stored in
their respective .FON files.

BAUD rate is also something that will normally be attached to a
FON record and used when dialing the record.  This is of more
concern to users of modems that do not allow LOCKING the port.

LOCK BAUD is almost always available as an option when using a
modem that can support CONNECT rates above 2400 baud.  When using
the LOCK BAUD option, AceComm will leave the port speed alone
when dialing.  The modem handles speed translation between
'connect' and 'computer'.  LOCK BAUD ON is generally preferable
with modems that support it.  The status displays will reflect
'L' appended to the baud rate when LOCK BAUD is set ON.  NOTE:
the 'L' is not appended in the Line Control Window's display
above.


o Connect speeds such as 12000, 14400 etc. are not actual
  data rates that the UART (serial port)  can be set to.

o Modems capable of connecting at 9600 and above can usually be
  used with a "Locked port"

o Setting the Baud rate to 19200 for a 9600 baud modem will
  allow better performance when down loading data.

o Locking the port means selecting a baud rate higher than the
  highest connect speed the modem is capable of, and telling the
  communications software to lock it there.

o Using a locked port requires your modem be in full handshake
  mode.


   "14.4k, 16.8k modems"

  Q.) Why doesn't AceComm support my 14.4k modems connect speed
      of 14400 in the "Baud Select" menu?

  A.) 14400 is a data rate your modem is capable of. The serial
      port in your computer cannot be set to 14400 baud.
      In order to operate at 14400 connect speeds, the serial
      port must be set to 19200, 38400, or 57600 baud.

      o  14400 is your modems "Connection Rate"
         "Line Speed", "Modem-to-Modem Speed", "DCE Speed" are
         other synonyms for "Connection Rate"

      o  19200 is the closest "Computer Rate"

      o Selecting the closest "Computer Rate" is called using
        a "Locked" port

        When using a "Locked" port your modem makes the
        translation between "Connection Rate" and "Computer
        Rate" by using FLOW control (RTS/CTS hardware
        handshaking)
        Your serial port can be set to 19200, or 38400 and left
        there (See LOCKBAUD)



   "Selecting your highest port speed when LOCKing the port"

  Locking the port at 57600 with a high speed modem causes the
  UART to assemble a character off the bit stream VERY quickly.

  If you experience serial input errors with HIGH locked rates,
  drop down to 38400 or even 19200.  The lower rate will cause
  the UART to make characters available at a reduced speed.  For
  instance a 12 MHZ AT will probably experience data overruns
  using a locked port above 19200 when down loading TEXT files
  with ZMODEM.

  A common miss-conception is when CRC errors occur with HIGH
  LOCKED PORT rates, that it is the UART unable to keep up.  This
  is simply not true.  The UART/modem combo is capable of out
  running the computer/software combo.  When using a TASK
  switcher such as WINDOWS or DESQVIEW, a lower PORT RATE such as
  19200 may very well be needed for efficient data transfers.

  The idea is to set the port to a speed that the
  computer/software combo is capable of responding to quickly
  enough.



o There is no order of sequence for these strings

o Connect strings will allow non-locked ports "auto adjust"

AceComm will detect a connection after dialing, a few seconds
quicker when able to match a connect string with the modem's
connect message.

High Speed modem users may configure the modem for more than 1
connect message to be returned from the modem.  AceComm need only
detect 1.  The connect string fields are freely configurational,
and follow no specific order.  Leave them, or edit them as needed
any way you see fit.

AceComm will fall out of re-dial on detection of CARRIER.  For
the LOCK BAUD users, this detection is right away.  For those who
use modems that don't allow port LOCKING, and want auto baud rate
adjustment to match the connect, CARRIER is checked only after
the dialing has timed out.  AceComm will be trying it's best to
get a CONNECT string so that the baud can be verified.


   ╔═════════ACE.PRM Data  Edit-Menus═══════╗
   ║ General Controls                       ║
   ║╔═══ Serial Port Setup Menu ═══════════╗║
   ║║ Port Number Select      1            ║║
   ║║ Line Control Setup      19200L,8N1   ║║
   ║║ Modem Connect Strings                ║║
   ║║╔═Modem Response Strings════════════════════════╗
   ║║║MDM_RESPONSE_OK           OK                  ║
   ║║║ MDM_RESPONSE_RING         RING                ║
   ║║║ MDM_RESPONSE_NO_CARRIER   NO CARRIER          ║
   ╚╚║ MDM_RESPONSE_ERROR        ERROR               ║
     ║ MDM_RESPONSE_NO_DIAL_TONE NO DIAL TONE        ║
     ║ MDM_RESPONSE_BUSY         BUSY                ║
     ║ MDM_RESPONSE_NO_ANSWER    NO ANSWER           ║
     ║ MDM_RESPONSE_RINGING      RINGING             ║
     ║ MDM_RESPONSE_VOICE        VOICE               ║
     ╚═ Edit  Quit ══════════════════════════════════╝

o AceComm uses text response strings only

Modem response strings are normally UPPER CASE.  Response strings
are used by AceComm when dialing to more quickly respond to BUSY,
NO CARRIER etc.  HOSTMODE will be waiting for a RING code.(1) The
Response strings that can be matched while dialing are displayed
in the DIAL WINDOW as they come in.



(1)  HOSTMODE  also  uses the UART's modem status register RI bit
     when detecting "RING".


o Cmd Terminator is automatically appended to modem command
  strings.

Here we have the modem commands AceComm uses to interact with
your modem.  Please note the bottom of the menu contains the "Cmd
Terminator".  AceComm appends this to all modem commands
automatically.  Notice that "Init" has a ^M followed by ~~~~ and
another command.  This is an example of command stacking.

'^' is an escape character AceComm recognizes and translates byte
following into control characters.  ^M translates into a carriage
return, <CR>, (13d).  A character following '^' is either upper
case or made upper case by AceComm, then subtracted by 64
converting 'A' to 1 etc.

'~' translate into 1/4 second delays.

AceComm modem command lines are limited to 40 characters in
length, including the Cmd Terminator.  This is a standard maximum
command length used by modem manufacturers.


o Video Terminal emulation is built into AceComm

o Associated KTS file is the Keyboard Translation Sequence file
  that will be loaded for the given Video Type.

o Keyboard Terminal emulation is defined inside of *.KTS files
  AceComm includes a separate utility KTS.EXE which allows the
  user to define KTS files for any Keyboard Terminal emulation
  desired.

AceComm emulates the selected VIDEO type.  "Associated KTS file"
is the .KTS file you want to use with the VIDEO selection.  Each
time AceComm activates a VIDEO type, the associated KTS file is
loaded and becomes active on the keyboard.  KTS keyboard
definitions override MACRO assignments.

KTS (Key Translation Sequence) files contain assignments for
a sequence of characters to a key press. When a key is pressed
from inside TERMINAL area, AceComm first checks to see if the
key press has been defined in the current KTS data. If so,
AceComm sends the assigned sequence of characters to the modem.
The utility KTS.EXE (included) can be used to create new and or
custom KTS files. See the included .ASC examples for defining
and creating KTS files. Using KTS.EXE, the keyboard can be
deigned to emulate any possible combination of characters
available to the system.
Key press assignments defined in the KTS data area are given
top priority, and thus take presides over MACROS assigned to
the same key.



KTS files contain a sequence of bytes to be sent to the modem
when a particular key press is made.  AceComm emulates a video
type independently from the keyboard emulation.  KTS files may be
edited to emulate any combination imaginable.  KTS files may be
created and assigned to a video type using the "Associate" option
above.

AceComm comes with ready made KTS files.

   Notes: .KTS files are compiled from .ASC files.  .ASC files
          may be created, maintained, customized with a TEXT
          EDITOR in ASCII TEXT mode.  The utility KTS.EXE is
          provided for compiling .ASC files into .BIN files.
          Rename the .BIN file with .KTS and copy the .KTS file
          into the directory pointed to in PRM-data for ".KTS".

o Each of the above key sets is available for assignment to a
  MACRO or MACRO stack.  The MACROS provide a wide range of
  services.  All of AceComm's functionality is available with
  MACROS.

o The "SHIFT-Fn" key-set is used by TAGGER to store TAGGED ITEMS


       Menu options here allow each key press be re-assigned.
       The keyboard can be arranged thru the use of MACROS to
       resemble software you are more accustomed to.  AceComm`s
       keyboard is totally MACRO driven.  Keyboard definitions
       are stored in .KBD files.  ACE.CTL can be edited so future
       upgrades of AceComm will automatically configure with your
       keyboard preference.


--Write--
  Prompts for a filename, and writes the current keyboard to a
  new KBD file, or updates an existing KBD file of the same name.
  When you choose "Write" the following occurs:
    AceComm  prompts  for  "filename"
    "filename"  is  forced a ".KBD"  extension
    "filename" is written in the same directory as ACE.PRM
    resides
    AceComm writes the contents of "Key MACRO Assignments" menu
    to the file
    AceComm re-reads the original KBD file.

  In short:
  - All changes, once written to a KBD file with "Write", pertain
    to the KBD file written to.
  - Making changes and not "Writing" them, will be saved to the
    current KBD file at program end.

To further explain, all changes made in this menu area to the
keyboard definitions, apply to the current KBD file.  If you exit
the menu area, without choosing "Write", and say "ACE_DEF.KBD" is
active, the changes will be stored to "ACE_DEF.KBD" when you
leave the PRM-data area.  If you choose "Write" from the above
menu, then the changes are stored to a new or existing KBD file,
and do not affect the current keyboard, as AceComm re-loads the
current KBD file after a "Write".  Unless you "Write" to the
current KBD file, which is un necessary, because AceComm will
update it automatically anyway.

"SHIFT-Fn" is the key-set the TAGGER function assigns TAGGED
ITEMS to.
When you tag a word or line from the screen, the tagged item
becomes associated with the first available SHIFT-Fn key by way
of the <SEND_SendStr> MACRO.

   ╔═════════ACE.PRM Data  Edit-Menus═══════╗
   ║ General Controls                       ║
   ║ Serial Port Setup                      ║
   ║╔═KeyBoard MACRO Assignments═══╗        ║
╔═ F# Keys ════════════════════════════════════════════════════
║  1<SendStr>Michael Phelps^M
║  2<SendStr>[FON_REC_PWD]^M
║  3<SendStr>Phoenix, AZ
║  4<SendStr>[PASSWORD]^M
║  5
║  6
║  7<SendAscii> %P
║  8
║  9
║ 10<SendStr>password^M
║11
║ 12<SendFile> message.txt
╚═══ Edit  Zap  Quit ══════════════════════════════════════════

- Edit
  Allows editing the MACRO assignment.

- Zap
  Clears field (Zaps) the MACRO assignment.

- .FON
  Where AceComm expects .FON files to be.

- .CAP
  Where AceComm will create and or re-open CAPTURE files.  A
  CAPTURE file is a means for "capturing" all port I/O to DISK.
  When you open a capture file, AceComm records everything that
  comes into the serial port, exactly as it comes in.  No
  filtering, no translation of any kind.(1) AceComm does not
  overwrite CAPTURE files.  You have the option of renaming the
  file, or AceComm will append new data to the end of the
  file(2).

- .SCR
  Where  AceComm  will  create  and  or look for .SCR files.  The
  MACRO <RunScript_> lists this directory.

- .KTS
  Where AceComm expects to find it's KTS files.  It's ok to store
  your .ASC files in this directory.

- Downloads
  This is the directory that AceComm 's internal protocols will
  receive into.  AceComm will also list this directory when
  building upload LISTFILES.

- Nodelist
  When you select the FileRequest option, AceComm expects to find
  either (a) a valid RAW FIDO NODELIST and NLIST.IDX file(3).
  or (b) a .NOD file(4)

- .REQ/.FLO
  Mailer  activities.

  .REQ files are used when doing File Requests.  When you ask
  AceComm to make a File Request, the filename is created using
  the NET/NODE number in ascii hex, and the file extensions is
  ".REQ".

  .FLO files (Mail List File) are used when you want to Fil
  Attach to a NET/NODE.  File Attach may be any file(s), and will

  mail bundle to the HOST.

(1) ANSI.EXE is a provided utility that can filter VIDEO CONTROL
     SEQUENCES from DISK files.

(2) If you have edited a CAPTURE file, or by other means used any
     utility that added the 26d character to the file, AceComm
     will not overwrite the END OF FILE character.  This may
     result in some editors not recognizing new data that follows
     the 26d character.  There exists utilities that can filter
     this and other characters from TEXT files.

(3)  NLIST.IDX is a file created using the AceComm utility
     IDX.EXE.  IDX.EXE will create a small index into the RAW
     FIDO NODELIST file, for all ZONE:NET pairs.

(4) .NOD files are FBL output for a NET.  FBL.EXE is another
     AceComm utility.


╔═Auto Engage Sequence Triggers═════════════════════════════════
║═Sequence Trigger -- Responding MACRO STACK════════════════════
║rz^M**^X           <RecvZmo>
║ HS*^B              <RunProgram>hslink -P1 <SendStr>^M
║  ^H ^H ^H ^H       <RunProgram>bimodem bimodem.pth <SendStr>^M
║ MPt ^V^H           <RunProgram>MPT R <SendStr> ^M
║
║
║
║
║ **EMSI_REQA77E     <SendEMSI_CLI>
║ **EMSI_IRQ8E08     <SendEMSI_ICI>
║═Pre/Post AutoM MACROS═════════════════════════════════════════
║
║
╚═══ Edit  Quit  Help ┤<>v^├════════════════════════════════════

o The last byte in a Sequence Trigger is the sequence scan
  trigger byte

o The last byte in a Sequence Trigger should end in an un
  common character (as designed above)

o EMSI_REQ detection can allow swift access to a BBS when
  mailer software answers the phone

o EMSI_IRQ is sent by BBS software to tell the caller it can do
  Interactive EMSI data handshaking

  The above defaults have been working very well for the
  protocols associated.


- Sequence Trigger
  A sequence trigger is a character string that is used by a
  remote HOST, protocol etc. as an attempt to engage some
  action from the other end.

- Trigger Character
  AceComm scans back thru it's receive buffer for a trigger
  sequence with each occurrence of the "last byte of the
  sequence".  This means that AceComm will scan for the string
  each time it sees the trigger byte arrive from the modem.  For
  this reason a sequence trigger will end in a non-common byte.
  While 'rz^M' (^M being <CR>, 13 decimal) would be a valid
  sequence trigger, we don't want AceComm to search on every
  carriage return character that comes in.  Look at Bimodem's
  sequence trigger, we don't want to end the sequence with a <SP>
  character (^' is the control code for SPACE CHARACTER 32
  decimal).

  Characters 32(Space) and below need be escape encoded with
  the '^' ^A becomes 1, ^B 2, ^C 3, ^M <CR>, ^` 32 <SP> etc.
  When entering sequence text, you may simply type the <SP>
  character, AceComm will do the conversion for you.

      **EMSI_REQA77E
  Most FIDONET mailer software will send an EMSI_REQ string to a
  caller.  This string is an attempt to determine the caller
  type.  AceComm's <SendEMSI_CLI> MACRO tells the mailer this is
  a human caller, bypassing the common "Press ESC to enter BBS"
  prompt.  DBridge mailer software is in complete and won't
  recognize this advanced EMSI handshaking.  All other mailer
  software does.

      **EMSI_IRQ8E08
  IEMSI capable BBS systems will send an EMSI_IRQ string to a
  caller.  Detection of EMSI_IRQ is responded to with IEMSI data
  handshaking.  AceComm's <SendEMSI_ICI> MACRO handles IEMSI log
  on.  (see PRM-data IEMSI Setup menu)

- Responding MACRO Stack
  The MACRO defined to the right of each sequence trigger will be
  used when a sequence has been detected.  This allows AceComm to
  be configured with auto download detection for up to 10
  protocols.  MACRO STACKING is valid with AutoM MACROS.

  The sending of a carriage return as the last macro is use full
  for moving the BBS display upon return from the external
  protocol.  AceComm completely disables the serial port before
  calling any external programs.

- PreAutoM MACRO
  The "PreAutoM" MACRO, if defined, will be processed prior to
  the AutoM MACRO about to be processed.  This allows for some
  extra maneuvering to be done which might otherwise be common to
  all AutoM MACROS anyway.  For instance the practice of changing
  to your "FILES" directory will insure that downloads are
  received into the "FILES" directory, even with protocols that
  do not allow file redirection.

  Notes: If you use PreAutoM MACRO for changing directories,
         remember that protocols such as BIMODEM which you may be
         up loading with at the same time, will need full path
         names to files they are to send.  Also protocols or what
         have you that use PRM, CFG etc.  files need know where
         to find these control files.

- PostAutoM MACRO
  The "PostAutoM" MACRO, if defined will be processed immediately
  following the AutoM MACRO.  Again this is some extra MACRO
  processing power for those common to all AutoM MACRO jobs.

- To Disable Auto Engage Sequence Triggers
  Located in the "Terminal Area Options" is a over ride flag with
  which Auto downloads may be completely disabled.  This flag
  affects all Sequence Trigger / AutoM MACROS pairs defined.

  Auto Engage                            On    <=-ENABLE
  Auto Engage                            Off   <=-DISABLE

┌─Intelligent Auto Log On Technology (Tm)───────────────────────
│─Trigger Sequence -- Responding Macro Stack────────────────────
│is your nAmE:       <SendStr>[USER_NAME]^M~Y^M~[FON_REC_PWD]^M
│ Your FIRST name:    <SendStr>[USER_NAME]^MY^M~[FON_REC_PWD]^M
│ Host Name:       <SendStr>CIS^M~~75120,3306^M~~[FON_REC_PWD]^M
│ first name ?        <SendStr>[USER_NAME]^MY^M[FON_REC_PWD]^M
│ and LAST name:      <SendStr>[USER_NAME]^M~^M~[FON_REC_PWD]^M
│ last name?          <SendStr>[USER_NAME]^M~~[FON_REC_PWD]^M
│ first name?         <SendStr>[USER_NAME]^M~~[FON_REC_PWD]^M
│
│
│
│─Case is Off───────────────────────────────────────────────────
└─── Edit  Toggle_Case  Quit  Help ┤<>├───────────────────────

o Each Fon.Record FLAGS can be toggled to perform auto log on
  by either use of a script file, or character sequence trigger
  and associated macro stack.

o AceComm responds to a sequence trigger by processing the macro
  stack.

o Log on sequence trigger scanning is available immediately after
  connect, and until the sequence has been found, or 2 minutes of
  on line time has passed.

o When a log on sequence has been processed, or 2 minutes of on
  line time has passed AceComm stops scanning for log on
  sequences for the remainder of the on line session.

o Sequence triggers are optionally CASE or nO cASE sensitive

On Dial/Connect Acecomm will, if the AutoL flag for the
current Fon.Record is SET, begin scanning incoming data for
Auto Log On Sequence Triggers. When any of the 10 possible
sequences is found, the sequence's associated macro stack is
processed.
Once a sequence has been found, scanning stops until the next
Dial/Connect.
If a sequence has not been found after the first 2 minutes of
on line time has passed, Intelligent Auto Log On (Tm) is
disabled until the next Dial/Connect.

- Toggle_Case
  The setup menu contains an option where sequence trigger
  scanning can be made case sensitive. AceComm's default setup
  is for scanning to be not case sensitive.

- Sequence Trigger
  A sequence trigger is a character string that is used by a
  remote HOST, protocol etc. as an attempt to engage some
  action from the other end.

- Trigger Character
  AceComm scans back thru it's receive buffer for a trigger
  sequence with each occurrence of the "last byte of the
  sequence".  This means that AceComm will scan for the string
  each time it sees the trigger byte arrive from the modem.  For
  this reason a sequence trigger will end in a non-common byte.
  While 'rz^M' (^M being <CR>, 13 decimal) would be a valid
  sequence trigger, we don't want AceComm to search on every
  carriage return character that comes in.  Look at Bimodem's
  sequence trigger, we don't want to end the sequence with a <SP>
  character (^' is the control code for SPACE CHARACTER 32
  decimal).

  Characters 32(Space) and below need be escape encoded with
  the '^' ^A becomes 1, ^B 2, ^C 3, ^M <CR>, ^` 32 <SP> etc.
  When entering sequence text, you may simply type the <SP>
  character, AceComm will do the conversion for you.

- To Disable Auto Log On Sequence Triggers Located in the
  "Fon.Record Edit" FLAGS menu is a over ride flag with which
  Auto Log On for the record may be completely disabled.  This
  flag only affects the currently selected record.

 Closer Look

 is your name:       <SendStr>[USER_NAME]^M~Y^M~[FON_REC_PWD]^M
  |                   |        |                 |
  |                   |        |                 Fon.Record
  Sequence Trigger    |        |                 password field
                      |        |
                      |        IEMSI data field
                      |
                      Associated macro stack

 AceComm provides two different data macros for passwords

   [PASSWORD]  represents the IEMSI password field

[FON_REC_PWD]  represents the current Fon.Record
               password field

Fon.Record password fields can be cloned for the entire FON
file using the "Mass_change" menu selection from inside the
Telephone directory list area.


o Electronic Mail Standard Identification (EMSI)

o EMSI is a widely used handshake protocol used with FIDONET
  mailer software

o Interactive Electronic Mail Standard Identification (IEMSI)

o IEMSI is an auto log on interface designed to present caller
  information to the HOST quickly and automatically. Few BBS
  systems currently support IEMSI. RA supports IEMSI log on.

o Interactive EMSI log on function is called with the
  <SendEMSI_ICI> MACRO function

o Data defined here will be used by the <SendEMSI_ICI> MACRO
  function

o All IEMSI data need not be defined. The BBS system will
prompt the user for any invalid or missing information.

EMSI handshake data

   The following data is presented to the remote mail system
   during EMSI handshaking.
   Address
   Sys Name AceComm Support
   City Phoenix, AZ
   Operator Michael Phelps
   Sys Phone (602) 846-2940
   Baud 14.4
   Flags v32b

   Password  --  Pre arranged between two systems.
   The following example will cause AceComm to fill in the EMSI
   data field for "password" with 'mailman' when the target
   system's address is 1:114/12.
                  Password 1:114/12 mailman


IEMSI handshake data

- User Name and Alias
  Enter your name as you want it to appear to a BBS system.
  There is also a  PRM-data  MACRO  [USER_NAME]  that  uses  this
  field.
  There is also a PRM-data MACRO [ALIAS] that uses this field.

- Location
  City, State, Country
  There is also a PRM-data MACRO [LOCATION] that uses this field.

- Data # and Voice #
  If  you have no Data #, leave the field blank.  There is also a
  PRM-data MACRO [DATA_PNUM] that uses this field.
  There is also a  PRM-data  MACRO  [DATA_PNUM]  that  uses  this
  field.

- Password
  This is a default password, any FON.RECORD.PASSWORD always will
  override this IEMSI PASSWORD.
  There is also a PRM-data MACRO [PASSWORD] that uses this field.

- Birthdate (currently unused)

- CRT def    (current session only)

      ╔═CRT Def═════════════════╗
      ║AVATAR/0+ / ANSI        ║
      ║ ANSI X3.64              ║
      ║ TTY (raw mode)          ║
      ╚═══ Select  Quit ┤<>v^├══╝

  Consists  of  four sub-fields separated by commas, from left to
  right:TERMINAL EMULATION,ROWS,COLUMNS,NULS
  AceComm fills in the ROWS,COLUMNS,NULS fields automatically
  when building IEMSI data packets.

                       Example CRTDEF: AVT0,24,80,0

  TERMINAL EMULATION
  Video type
                              AVT0        (AVATAR/ANSI)
                              ANSI
                              TTY
  ROWS
         Video rows for current session only
  COLUMNS
         Video columns for current session only
  NULS
         00h character required after line feeds.

- Protocols
  ╔═Protocols═════════════════════════╗
  ║ZedZap (Zmodem to 8k)        Yes  ║
  ║ Zmodem                       Yes  ║
  ╚═══ Select  Quit ┤<>v^├════════════╝

  AceComm internal protocols support ZMO,ZAP fields.
  ZMO is normal zmodem
  ZAP is zmodem with up to 8k data frames.

- Capability    (current session only)
  ╔═Capabilities══════════════════════╗
  ║Can do full screen chat      Yes  ║
  ║ Can handle TAB characters    Yes  ║
  ║ Can handle 8-bit characters  Yes  ║
  ╚═══ Select  Quit ┤<>v^├════════════╝

  CHT       Can do full screen on line conversation (CHAT)
  TAB       Can handle TAB (ASCII 09h) characters
                  AceComm supports TAB
  ASCII8    Can handle 8-bit IBM PC ASCII characters

- Requests      (current session only)
  ╔═Requests══════════════════════════╗
  ║Show bulletins,announcements Yes  ║
  ║ Check for new mail           Yes  ║
  ║ Check for new files          Yes  ║
  ║ Hot-keys                     Yes  ║
  ║ Screen clearing              Yes  ║
  ║ Do not disturb               Yes  ║
  ║ Page pausing, `More`         Yes  ║
  ║ Full-screen editor           Yes  ║
  ╚═══ Select  Quit ┤<>v^├════════════╝

  NEWS      Show bulletins, announcements, etc.
  MAIL      Check for new mail
  FILE      Check for new files
  HOT       Hot keys "ON"
  CLR       Screen clearing
  HUSH      Do not disturb
  MORE      Page pausing, often referred to as "More"
  FSED      Full screen editor

AceComm  contains  internal Xmodem, Xmodem 1k, Ymodem, Ymodem 1k,
Ymodem G, Zmodem, and a Zmodem variant ZedZap (8k).

--Internal Batch Capable--
  Batch protocols receive the incoming filenames as part of the
  file data sent from the sender.  AceComm will append filenames
  received from the remote sender to the directory path contained
  in the PRM-data area under "FILES".

--Internal Single File--
  Single file protocols require a filename be given locally, by
  the user.  The user is prompted for a filename between the menu
  selection and calling the internal protocol function.

--External Menu--
  "Externals" are defined as menu selectable executable that will
   become arguments to the <RunProgram> MACRO.

   You may find it simpler to assign external protocols to a "Hot
   Key" from inside PRM-data Key Definition menu.  This menu is
   provided for those who want a "menu driven" affect.

--Auto Engaging Menu--
  AutoDnlds are protocols whose sending units begin by sending a
  documented sequence of characters.  AceComm allows up to 10
  separate sequences be defined, and associates each sequence
  with a MACRO STACK.  the MACRO STACK can be setup to call the
  external protocol associated with the sequence.  "AutoDnLds" is
  documented in more detail above.  Shown below is a snippet
  reminder display.

  ╔═ AutoDnLd Sequence Triggers ═════════════════════════════════
  ║ rz^M**^X            <RecvZmo>
  ║ HS*^B               <RunProgram>hslink -P1 <SendStr>^M
  ║  ^H ^H ^H ^H        <RunProgram>bimodem /C \ace <SendStr>^M
  ║ MPt ^V^H            <RunProgram>MPT R <SendStr> ^M
  ║ at is your name:    <SendStr>Michael Phelps^M~^M~PASS^M
  See "AutoDnLd Sequence Trigger" menu for more information.

--Recv Mail / File Request--
  "FileRequest" is a point mail function.
  Selecting File Request function will bring up the menu below
  if the PRM-data directory field for NODELIST points to either
    - FIDONET NODELIST and compiled NLIST.IDX file
    - FBL.EXE output .NOD file
  FBL output .NOD file is used in the example below.

 ╔═══════════════════════════════════════╗
 ║           1:114/12                   ║
 ║ Format =>  ZONE:NET/NODE              ║
 ╚═══════════════════════════════════════╝
 This menu prompts the user for a ZONE:NET/NODE number of the
 system we want to call. Having entered the above "1:114/12"
 the menu below is presented.

 ╔═1:114/12══════════════════════════════╗
 ╔═D:\ACE\fon\══════════════════════════╗║
 ║  1_105.NOD    19595   05/12/93 10:09 ║║
 ║ 1_114.NOD    11220   05/12/93 10:09 ║╝
O║  1_125.NOD    7886    05/12/93 10:09 ║
 ║  1_282.NOD    7623    05/12/93 10:09 ║
O║  1_382.NOD    10291   05/12/93 10:09 ║
 ╚═│Grab│ Quit ┤<>v^├═══════════════════╝
 This menu lists FBL output .NOD files found in the directory
 field NODELIST.  FBL produces these files and names them
 according to their ZONE_NET number.  We want to select the file
 1_114.NOD because 1_114.NOD is an extracted listing of all NET
 114 zone 1, from the FIDONET NODELIST.  Selecting the 1_114.NOD
 file produces the following menu.

 ╔═1:114/12══════════════════════════════╗
 ║╔═1:114/12═══════════════════════════════════════════╗
 ║║    System Name ORAC/2                              ║
 ╚║           City Phoenix_AZ                          ║
  ║  Operator Name Eugene_Glover                       ║
  ║   Phone Number 1-602-277-1334                      ║
  ║      Baud Rate 9600                                ║
  ║          Flags H16,CM,XA                           ║
  ║ .CFG  Password mailman                             ║
  ╚═│File_Request│ Human call  Poll_for_Mail  Quit ════╝

 Here AceComm has found the desired node information from the
 file 1_114.NOD.

 Notice the "Phone Number" field contains a long distance
 number.  The following "Dial Filter" statement" contained in
 "Point Mail Setup" menu is used to convert the phone number to a
 local number.
      1-602-
       (A)        (B)
 Explanation: Field (A) defines what to look for in phone numbers
              Filed (B) defines what to replace field (A) with.
              Here we left field (B) blank.  AceComm then
              replaces "1-602-" with nothing.

 Notice the "Password field. The following "Password"
 definition was made in "Point Mail Setup" menu.
      1:114/12 mailman

 The selector bar at the bottom of the above menu contains
 several choices. The first being "File Request". Selecting
 "File Request" produces the following screen.

 ╔═Input Window═════════════════════
 ║══════════════════════════════════
 ║FileName:  files
 ╚══════════════════════════════════

 AceComm is prompting for file names.  The example uses the file
 name "files".  Many systems will recognize "files" as a MAGIC
 file name, and send an "all files listing" for the system in
 response. Pressing <ENTER> alone when finished entering file
 names causes AceComm to begin dialing the target system.

     ╔══Record Number 1:114/12══════════════════════════════════
     ║     System Name   ORAC/2
     ║     Phone Number   1-602-277-1334
OK   ║     Line Control   9600L,8N1
     ║       Video Type
OK   ║ Control Flags      AutoMACRO,
     ║      Dial Prefix
     ║     Log on Script
     ║     Capture File
     ║         Password   mailman
     ║    Load KBD File
     ║  Log on triggers
     ║═Last Connect  --   Total Connects ═══════════════════════
     ║ 0
     ║═Cycles     --      Dial String                       Last
     ║   0                ATEQ0X4DT277-1334
     ║ 00:03    00:03     58
     ╚═│Quit│ <SpaceBar>-ReCycle ┤<>v^├═════════════════════════
----------------------------------------------------------------
CONNECT 9600/ARQ
 Address 1:114/12 Using BinkleyTerm-OS/2 Ver. 2.56

Welcome to ORAC/2 - Home of Log/2 (Log for OS/2)
Press <escape> to enter BBS!
ORAC/2
Eugene Glover, Phoenix, AZ USA1-602-277-1334
BinkleyTerm, 9600, CM,XA,V32B,HST

  Outgoing  D:\ACE\mail\0072000C.REQ
 File Info  7 06/26/1993 11:55
0        7        0 CPS        00:00        ZEOF
                 CPS                ZDATA
  Incoming  c:\fil\orac.lzh
 File Info  90401 06/24/1993 20:00
90401        289        1089 CPS        01:23        ZSendHexHdr
TIMEOUT

NO CARRIER

OK
----------------------------------------------------------------
AceComm uses it's text based display for the Point Mail protocol
displays.

AceComm  contains  internal Xmodem, Xmodem 1k, Ymodem, Ymodem 1k,
Ymodem G, Zmodem, and a Zmodem variant ZedZap (8k).

--Internal Batch Capable--
  AceComm's internal "Batch" capable protocols are capable of
  sending from a LISTFILE.  A LISTFILE is an ascii text file
  containing <CR> <LF> terminated filenames.  One filename per
  line.  Filenames may contain a full DRIVE:\PATH specifier.
  AceComm looks in the current directory for a filename
  "UPLDS.LST".  When selecting any of the "Batch" capable
  internal sending units, AceComm will always look for
  "UPLDS.LST", if the file exists, AceComm displays the following
  screen.

 ╓─────────────────╖      AceComm always prompts to send the
 ║ Found UPLDS.LST ║   from the LISTFILE "UPLDS.LST", when the
 ║ Send contents?  ║   "UPLDS.LST" file exists in the directory.
 ║(Y)es/(n)o?:    ║   Pressing <CR> defaults to (Y)es, (n)o
 ╙─────────────────╜   brings up the regular file selection
                       menu.


 ╓───────────────────╖      If the (Y)es selection was selected,
 ║ UPLDS.LST         ║   AceComm will, after the transfer,
 ║ Delete this file? ║   present the menu at left, prompting to
 ║(Y)es/(n)o?:      ║   delete the LISTFILE, or leave it exist.
 ╙───────────────────╜



The "Regular file selection" menu (below) allows "on the fly"
LISTFILE creation.  The "on the fly" LISTFILE is not named
"UPLDS.LST", but a temporary unique filename is selected.  "On
the fly" LISTFILE is deleted after transfer without any prompt.

     ╓─Make Uploads List────────────────╖
     ║Batch Tag                        ║
     ║ Manual entry                     ║
     ║ Finished  /  ESC-key             ║
     ╙─ Select  Quit ───────────────────╜

        Batch Tag
        This selection brings up the "FileLister" menu.  This
        menu allows tagging filenames to the LISTFILE.  PRM-data
        DIR "DNLDS" is the default directory displayed by
        "FileLister" when called by the "Sender Protocols" menu.

        Manual entry
        The  menu  below  is  presented  with the "Manual entry"
        selection.

  ╓─Make Uploads List─────────────────╖
  ║ Batch Tag                         ║
  ║╓─Input Window───────────────────────────────────────────────
  ║║FileName:  c:\fil\
  ╙║─Input Window<ENTER> alone when done────────────────────────
   ╙────────────────────────────────────────────────────────────
  The "Manual entry" filename prompt pre pends the prompt space
  with any PATH found in PRM-data DNLDS field.


  "Batch Tag/ Manual entry" are recorded to a temporary unique
  LISTFILE as explained above.  Temporary unique LISTFILE is
  automatically deleted after use.


  - Single File
    AceComm's internal protocols that send 1 filename per
    invocation use the "Manual entry" window shown below.

  ╓─Input Window───────────────────────────────────────────────
  ║FileName:  c:\fil\
  ║─Input Window<ENTER> alone when done────────────────────────
  ╙────────────────────────────────────────────────────────────

--Externals--
  This selection brings up a menu listing up to five
  configurations for external protocol setup/selection.  This
  menu allows storing configurations for external protocols to be
  used.  The menu storage below functions the same as any MACRO
  stack assigned to a key press.  Here you have a menu where you
  may find it easier to to store specific upload protocol
  definitions.

 ╓─ External Protocols (UpLd) ──────────────────────────────────
 ║<RunProgram>BIMODEM %WK
 ║ <RunProgram>HSLINK %PF %WK
 ║ <RunProgram>MPT S @UPLDS.LST %WK
 ║ <RunProgram>JMODEM S %PF %WK
 ║ <RunProgram>DSZ sz %PF
 ╙─ Select  Edit  Quit ─────────────────────────────────────────


-- Send Mail / File Attach--
  This selection allows the user to send files to EMSI capable
  mailer software.  The menu shown below prompts the user for a
  FIDONET style ZONE:NET/NODE number.

 ╓───────────────────────────────────────╖
 ║                                      ║
 ║ Format =>  ZONE:NET/NODE              ║
 ╙───────────────────────────────────────╜

  The number is required for naming a LISTFILE.  LISTFILE in this
  mode uses "FLO" file extension.  AceComm allows normal Tag or
  manual entry when adding filenames to LISTFILE.  Those who want
  to "File Attach" or are running under a HOST as a point mail
  system will use this option.  Point mail operators may upload
  their mail bundles with this "Send Mail" selection.  AceComm
  requires a NODELIST or FBL output .NOD file when using "Send
  Mail/Attach".  AceComm uses the ZONE:NET/NODE number entered
  above for looking up system information about the HOST to be
  called.  AceComm is able to retrieve the phone number and
  system name from NODELIST/.NOD files.

  
The Telephone Directory Area lists binary .FON files in their
full ASCII representation.  The current loaded .FON file is
identified at the top of the menu.  Notice that the number of
records contained in the '1_114.FON' file is presented at the top
right.  .FON files are not fixed to any certain record size, and
can have records added or deleted, from here, in the Directory
list area.  Maximum record count for a FON file is 1000 records
per FON file.  AceComm supports unlimited FON files, and provides
easy directory List/Grab function for changing FON files.

- Dial
  Dial the "highlighted" record.  The function continues dialing
  until:

     (a) a connection has been established

     (b)  USER ABORT.

- Edit
  Another menu contains the "highlighted" record's data is
  presented for editing, or just a closer view.  All changes are
  automatically save to disk.


- <SP>-Que
  Mark the "highlighted" record for 'RedialQue'.

- Circular_dial_Queue
  Switch into The 'Que' Menu.  At least 1 record needs be marked
  "Queued" for AceComm to present this area.  From the 'Que'
  Menu, 'Dial' goes into single dial mode, and each record is
  dialed 1 time, followed by the next record until all records in
  the 'Que' have been dialed.  The 'Que' then revolves around to
  the first record and begins again.  When a connection has been
  established, the record is removed from the 'Que'.

╔═ Circular_Redial_Que D:\ACE\1_114.FON, 6 Records══════════════
║═      System Name            Phone Number     Line Control Vid
║14  Artemis Lair bbs         1-602-841-4474     9600,8N1    A
║ 15  Astroland                1-602-381-8708     9600,8N1    A
║ 16  Bob's Place BBS Node 1   1-602-497-2173     2400,8N1    A
║ 17  Bob's Place BBS Node 2   1-602-545-8745     9600,8N1    A
║ 18  Broadcaster's BBS        1-602-872-9148     9600,8N1    A
║ 19  CADE BBS                 1-602-931-3468     2400,8N1    A
║  Dial  Edit  <SPACEBAR>-Zap  Telephone_Directory
╚═ Add_record  Remove_record  UnMark_All  Import  Paint  Quit ┤<

-Fon_files
  List PRM-data directory .FON, allow selection of new .FON file

- Sort
  ┌─Sort FON file by ?─┐
  │Number of calls    │
  │ Last date called   │
  │ System name field  │
  │ System number      │
  └─── Select  Quit ───┘

- Options
  ┌─Dialing Options───────────────────────────────┐
  │Inter byte delay                         1    │
  │ Modem Response Timeout when dialing      60   │
  │ Seconds between re-dial                  1    │
  │ DTR state between re-dial                Off  │
  │ Ring BELL on Dial/Connect                1    │
  └─── Select  Quit  Help ┤<>├──────────────────┘

- Add_record
  Function appends a new record to the current loaded .FON file,
  and immediately brings up the 'Edit' Menu.  The new record is
  automatically saved.

- Remove_record
  The "highlighted" record is removed  from  the  current  loaded
  .FON file.  No hole is left, the .FON file is reduced a 'record
  size' in bytes.


- Mass_Change
  ┌─Mass Change FON Records─┐
  │     Dial Prefix        │
  │         Password        │
  │    Load KBD File        │
  │     Line Control        │
  │       Video Type        │
  │    Flags Control        │
  │       UnMark All        │
  └─── Select  Quit ┤<>├──┘
  All records in a FON file can be updated at one time, with
  individual record member updates.

- Import
  o  Convert another software's FON type file to AceComm FON
     file.
  o  Merge two AceComm format FON files into one file.
  o  Initialize a new FON file of video rows number of
     blank records.

  "Import" selection brings up the FON file conversion menu
   displayed below. The menu provides the following functions.

  ┌─Covert to AceComm FON──────┐
  │                            │
  │ BOYAN    5                │
  │  Qmodem   4                │
  │  Qmodem   5                │
  │  Procomm  2.43             │
  │  PcPlus   1                │
  │  PcPlus   2                │
  │  Telemate 3.01 - 4.12      │
  │  TELIX    3.15 - 3.21      │
  │  Combine 2 Ace FON         │
  │  Create blank FON          │
  └─── Select  Quit ┤<>├─────┘

- Paint
  Customize the current menu only.  All changes are save
  automatically.

- Quit to Terminal Area. (ESC-key)


- System Name            AceComm Software Support
  The name defined here, is presented onto the revolving status
  line (right side of status line) when "on line".

- Phone Number           1-602-846-2940
  This  phone  number, although long distance, can be modified by
  AceComm when dialing, with use of "Dial" statements in the
  Point Mail Menu.

  Example: lets say we are local Phoenix, where our area code is
           602, we have an entire phone directory of long
           distance numbers.  The following dial statement
           defined inside "Point Mail Setup" will cause AceComm
           to translate all of the long distance numbers to local
           numbers.

           Dial 1-602-

           AceComm will see this definition and translate it into
           anything following the definition.  In this case, we
           did not put anything after the "1-602-", so AceComm
           will strip "1-602-" from all phone numbers that
           contain "1-602-" as part of the number.  This is valid
           for all phone numbers that are processed thru the
           AceComm Dialer Menu.  Mailer mode, File Requests which
           get their phone numbers from either a FIDO NODELIST,
           of FBL output .NOD file do use the Dialer Menu and do
           receive number translation from "Dial" statements.

- Line Control           2400L,8N1
  Most remote HOSTS will be set up using 8 data bits, No parity,
  and 1 stop bit.  Compuserve uses 7 data bits, Even parity, and
  1 stop bit.  AceComm will configure the UART to assemble the in
  coming bit stream into characters, based on the configuration
  defined here.  Baud rate means nothing when LOCKBAUD is set, as
  is with the "L" appended to baud in this example.  Other wise,
  when LOCKBAUD is not set, AceComm will set the UART up to the
  Fon.Record baud rate.

  Note: When LOCKBAUD is not set, AceComm is also capable of
        resetting the baud rate to a connect string.  If you dial
        out at 2400, and connect at 9600, and 9600 is detected in
        the the connect string, AceComm will automatically set
        the baud to 9600.  If LOCKBAUD is set, AceComm leaves
        baud alone.

- Terminal Emulation     Av/An
  This option will present the Terminal emulations menu, you may
  select the video ,type you want associated with this record.
  "Av/An means AVATAR and ANSI video emulation.

- Control Flags  Macro,DTag,Capture,Text,IEMSI,AutoL

       ╔═   Control Flags═════════════════╗
       ║ Tag dial attempts    On          ║
       ║ Auto log on method   Macro,      ║
       ║ Open Capture file on On          ║
       ║ Capture mode         Text,       ║
       ║Allow IEMSI log on   On          ║
       ║ Allow auto log on    On          ║
       ╚═══ Edit  Quit ┤<>v^├═════════════╝

  "Script"  when  set,
  AceComm will attempt to load and run the filename defined next
  to "AutoLogOn Script".  If a script file is not found, AceComm
  ignores the error and continues normal operation.
  Notes: .SCR files are looked for in the directory defined
  inside PRM-data Area "Directories"

  "Macro"  when  set,
  AceComm will enable the defined Auto Log on Sequence Triggers
  and corresponding MACRO stacks.

  "DTag"  when  set,
  AceComm will tag un-successful dial attempts (busy, etc.) to
  the Que Dialer.  An "*" character appears to the left of a
  Fon.Record's display line, when it is either Q tagged or, D
  tagged.  When this flag is not set, the only other way to Q tag
  a record is by manually selecting the menu option
  "<SPACEBAR>-Que" from the fon list display.

 "Capture"
 When this flag is selected, a capture file is opened upon
 Dial/Connect.  Any previously open capture file is first closed.

 "Raw"  when set,
 Data to capture file is as it comes in from the modem

 "Text"  when set,
 Data to capture file is filtered of video control codes
 as appilcable to the current Video type

 "IEMSI"
 Allow Interactive EMSI log on

 "AutoL"
 Allow auto log on methods (script/macro)


- Dialing Prefix
  The Fon.Record dial prefix overrides The PRM-data default
  prefix.  If this field is null (blank), AceComm uses the
  PRM-data default dial prefix.

- AutoLogOn Script       ACE_S.SCR
  When SCRIPT flag is set, for the current Fon.Record, AceComm
  will use this filename, opening it as a SCRIPT file, and run
  the contents.  This action takes place upon successful
  Dial/Connect.  If the filename does not exist, AceComm simply
  goes about it's business, and you will log on normally.
  AceComm will look for the SCRIPT filename in PRM-data DIR .SCR
  path.

- Capture File           ACE_S.CAP
  Default filename presented to user when opening a "capture data
  to file" file.

- Password               my/password
  See also: Expandable MACRO Parameters <SendStr> [FON_PASSWORD]
  would replace "[FON_PASSWORD]" with "my/password" for this
  example.  You may define the Fon.Record PASSWORD field to any
  character combination, the field maximum length is 19
  characters.

- Custom .KBD File       MY.KBD
  KeyBoard File, AceComm will first remember what the current KBD
  filename is, load the Fon.Record's custom KBD file, if defined,
  and finally restore the original KBD file after session
  disconnect.  Say What?

  You are about to log onto Compuserve.  You have CIS.KBD file
  defined for the Fon.Record.  When dial/connect is detected,
  AceComm will load the contents of CIS.KBD, overlaying your
  current keyboard MACRO assignments.  When you log off of
  Compuserve, and AceComm detects the carrier drop (no DCD),
  AceComm will load back the original keyboard file, overlaying
  your custom CIS.KBD.

  You will need to distinguish KBD files from KTS files.  Where a
  KBD file overlays the keyboard MACRO assignments.  The KTS file
  defines the ultimate sequence that will be sent to the modem
  for a given key-press.  Keys assigned a MACRO, are processed as
  MACRO functions.

  Keys not assigned a MACRO(s) will be sent to the modem, and are
  candidates for KTS.

  Keys with extended codes, are sent as they would be seen in
  DoorWay mode.  Normal keys (a-z,A-Z,1-0,CTRL A-CTRL Z, etc.)
  are sent in their normal lower ascii representation (as you
  would expect).  Now, any of these key-presses that have been
  defined inside the KTS file, are translated into their defined
  sequence.  AceComm & Utilities provides ASCII examples for
  compiling KTS files, as well as KTS.EXE the custom Keyboard
  Sequence Translation (Tm) compiler.

- Auto Log on Sequence Trigger/MACRO Stack
  Each Fon.Record can be assigned to one of the Auto Log on
  definitions available from a menu when selecting this option.
  AceComm will respond to a sequence trigger by processing the
  MACRO stack. Log on sequence trigger scanning is available
  immediately after connect, and until the sequence has been
  found. When a log on sequence has been processed, AceComm
  stops scanning for the log on sequence.

 ╔═D:\ACE═══════════════════════════════╗
 ║ 1_114.FON    26368   06/27/93 07:25 ║
 ║  ACE.ASM      8269    06/26/93 18:00 ║
 ║  ACE.CTL      13589   06/25/93 08:04 ║
 ║  ACE.EXE      196102  06/27/93 07:24 ║
 ║  ACE.FON      1600    06/27/93 04:13 ║
 ║  ACE.HLP      44572   06/27/93 07:09 ║
 ║  ACE.LOG      3694    06/27/93 07:29 ║
 ...
 ║  ACTL.ASM     101998  06/25/93 14:22 ║
 ║  Utility  New_Dir  Change_Drive      ║
 ╚═ Tag  Delete  Quit  Help ┤<>v^├══════╝

- Utility
  This selection brings up a sub-menu of pre-defined executable.
  AceComm contains several sub-menus for this purpose.  Sub-menu
  selected is determined by the "highlighted" files's extension.
  The %FN symbol is documented in MACRO.DOC.  %FN is an
  Expandable MACRO Function.  %FN argument to a MACRO from
  anywhere inside the "File Lister" menus is replaced with FULL
  PATH NAME for the current high lighted filename.

 ╔═C:\DOC═══════════════════════════════╗
 ║  A.SNA        1242    06/27/93 07:53 ║
 ║  ACE.BAK      117893  06/26/93 12:25 ║
 ║  ACE.CHA      2706    06/27/93 07:46 ║
 ║╔═%FN = C:\DOC\ACE.DOC══════════════════════════════════
 ║ ║ <RunProgram> BB %FN
 ║ ║<RunProgram> LIST %FN
 ║ ║ <RunProgram> QEDIT %FN
 ║ ║ <RunProgram> GREP %PF %FN %PF
 ║ ║ <RunProgram> PATCH %FN
 ║ ╚═ Select  Edit  Quit ┤<>v^├════════════════════════════
 ║  COVER        213     06/25/93 16:22 ║
 ║  CREDIT.CRD   2918    06/25/93 15:30 ║
 ...
 ║  FILE_ID.DIZ  392     06/26/93 13:14 ║
 ║  Utility  New_Dir  Change_Drive      ║
 ╚═ Tag  Delete  Quit  Help ┤<>v^├══════╝


- New_Dir
  Allows changing directories.  AceComm changes directories right
  along with the display.  When you use AceComm's  "Utils"  Menu,
  work is done in the currently listed directory unless otherwise
  redirected   via   MACRO   arguments   or  overriding  external
  executable configurations.

  Notes: AceComm always returns to the starting  directory  after
         leaving the FileLister Area.
                    ╔═D:\ACE═══════════════╗
 ╔═D:\ACE═══════════║D:\ACE              ║
 ║ 1_114.FON    263║ ..                  ║
 ║  ACE.ASM      826║ CAP                 ║
 ║  ACE.CTL      135║ CVTFON              ║
 ║  ACE.EXE      196║ FILES               ║
 ║  ACE.FON      160║ FON                 ║
 ║  ACE.HLP      445║ KTS                 ║
 ║  ACE.LOG      369║ MAIL                ║
 ║  ACE.MAP      920║ SCR                 ║
 ║  ACE.OBJ      271║ SND                 ║
 ║  ACE.PRM      378║ XTRA                ║
 ║  ACEBOX.INC   345║ ZEN                 ║
 ║  ACEM         253║ F                   ║
 ║  ACEORDER.FRM 588╚═ Select  Quit ┤<>v^├═╝
 ║  ACET.SCR     809     05/17/93 21:33 ║
 ...
 ║  ACTL.ASM     101998  06/25/93 14:22 ║
 ║  Utility  New_Dir  Change_Drive      ║
 ╚═ Tag  Delete  Quit   Help ┤<>v^├═════╝


- Change Drive
  Allows listing another drive.
 ╔═D:\ACE═══════════╔══════════════════════╗
 ║ 1_114.FON    263║A                    ║
 ║  ACE.ASM      826║ B                    ║
 ║  ACE.CTL      135║ C                    ║
 ║  ACE.EXE      196║ D                    ║
 ║  ACE.FON      160║ E                    ║
 ║  ACE.HLP      445╚═ Select  Quit ┤<>v^├═╝
 ║  ACE.LOG      3694    06/27/93 07:29 ║
 ...
 ║  ACTL.ASM     101998  06/25/93 14:22 ║
 ║  Utility  New_Dir  Change_Drive      ║
 ╚═ Tag  Delete  Quit  Help ┤<>v^├══════╝


- Tagged files
  Tagged files are stored in the file "UPLDS.LST" when tagged from
  inside the <FileLister_> MACRO.  When tagged from any of
  AceComm's internal protocol sending units, tagged filenames are
  stored into a temporary file.  The temporary file is deleted
  after each use.  UPLDS.LST files are not deleted, but instead
  stored ready.

  AceComm will look for UPLDS.LST when any internal batch capable
  protocols are selected.  If found, AceComm will ask the user is
  sending the contents of UPLDS.LST is desired, if (Y)es, AceComm
  will attempt to send all filenames listed in the UPLDS.LST file,
  if (n)o, AceComm will present the the File Input' menu.
 ╔═D:\ACE═══════════════════════════════╗╔═UPLDS.LST════════════
 ║  1_114.FON    26368   06/27/93 07:25 ║║D:\ACE\1_114.FON
 ║ ACE.ASM      8269    06/26/93 18:00 ║║
 ║  ACE.CTL      13589   06/25/93 08:04 ║║
 ║  ACE.EXE      196102  06/27/93 07:24 ║║
 ║  ACE.FON      1600    06/27/93 04:13 ║║
 ║  ACE.HLP      44572   06/27/93 07:09 ║║
 ║  ACE_MAIL.CFG 430     06/22/93 14:23 ║║
 ...
 ║  ACTL         591     06/22/93 14:08 ║║
 ║  ACTL.ASM     101998  06/25/93 14:22 ║║
 ║  Utility  New_Dir  Change_Drive      ║╚══════════════════════
 ╚═│Tag│ Delete  Quit  Help ┤<>v^├══════╝


- Delete
  Delete option presents a full path spec for the high lighted
  filename, prompting confirmation before deletion.
 ╔═D:\ACE═══════════════════════════════╗
 ║  1_114.FON    26368   06/27/93 07:25 ║
 ║╔═══════════════════╗ 06/27/93 07:31 ║
 ║ ║ D:\ACE\A.SNA      ║ 06/26/93 18:00 ║
 ║ ║ Delete this file? ║ 06/27/93 07:31 ║
 ║ ║(Y)es/(n)o?:      ║ 06/25/93 08:04 ║
 ║ ╚═══════════════════╝ 06/27/93 07:24 ║
 ║  ACE.FON      1600    06/27/93 04:13 ║
 ║  ACE.HLP      44572   06/27/93 07:09 ║
 ║  ACE_DEF.KBD  11120   06/27/93 07:29 ║
 ...
 ║  ACE_MAIL.CFG 430     06/22/93 14:23 ║
 ║  Utility  New_Dir  Change_Drive      ║
 ╚═ Tag  Delete  Quit  Help ┤<>v^├══════╝

      ┌─Point Mail Setup─────────────────────────────────────
      │ Boss Name  Boss Node
      │  Boss Addr  1:114/35
      │ Boss Phone  846-2940
      │   Boss Pwd  mailman
      │  Boss Baud  19200
      │  Nodelist   c:\fil
      │   Mail In   D:\ACE
      │  Mail Out   D:\ACE
      │─Sub Menus────────────────────────────────────────────
      │ Dial Trans
      │ Passwords
      └─── Edit  Quit  Help ┤<>├───────────────────────────

o  Boss data is used for mail Poll, Send, Request functions from
   inside the menu system (manual).  Automated mail functions
   require a NODELIST file and NLIST.IDX file.

 Boss Setup
   Define a system that you point mail from
   AceComm will allow selection of "Boss" from inside the
   Zone:Net/Node prompt menu.

 Dial filter  --  AceComm will use Dial statements to modify
   phone numbers. Dial filter statements are used when dialing
   from inside of AceComm's phone directory, and or with mail
   functions.
   A long distance BBS directory list can be used without
   editing phone numbers.

   ┌─Example: 1-602-454- 1-454───────────────────────────
   │Dial filter 1-602-
   │ Dial filter
   │ Dial filter
   │ Dial filter
   │ Dial filter
   └─── Edit  Quit  Help ┤<>├──────────────────────────


   The following dial statement filter "1-602-" from all phone
   numbers the  string is found in.
                  Dial filter 1-602-

   The following dial statement converts "1-602-451" found in
   phone numbers to "1-451".
                  Dial filter 1-602-451 1-451

   Dial statements are required when using point mail
   functions, because NODELIST phone numbers contain area
   codes. AceComm uses dial statements to know how to modify
   phone numbers.

 Password  --  When an address is pass worded, the EMSI password
 field will be used to relay the password to a remote system
 during mail sessions.

   ┌─Example: 1:114/12 mailman───────────────────────────
   │   Password
   │    Password
   │    Password
   │    Password
   │    Password
   └─── Edit  Quit  Help ┤<>├──────────────────────────



NODELIST DIRECTORY


Point mail functions look in the PRM-data directory "NODELIST"
  for systems directories.  Point mail functions require either
  of two types systems directories.

Systems directory type (FIDO  NODELIST)
  FIDO NODELIST is a systems directory that most EMSI capable
  HOST systems use.  AceComm can use a FIDO NODELIST.  To use the
  FIDO NODELIST, you must first compile an INDEX file.  AceComm
  uses NLIST.IDX.  NLIST.IDX contains a quick look up table for
  Zone:Net/Nodes in the FIDO NODELIST.  The AceComm package
  provides IDX.EXE as a utility to create the NLIST.IDX file.
  NLIST.IDX and the NODELIST are to be found inside of the
  PRM-data directory "NODELIST".


Systems directory type (FBL.EXE output .NOD file)
  NOD file is a NET extraction from the FIDO NODELIST.  FBL.EXE
  (provided) is capable of creating this file.  .NOD files
  contain a listing for a single NET.  .NOD files are very small
  and may be preferable for point mail use where calling 1 or a
  few pre know NETS is intended.  .NOD files are to be found
  inside of the PRM-data directory "NODELIST".


Automated Mail Services

  Automated (event driven) mail services require a
  NLIST.IDX,NODELIST.nnn pair be present in the NODELIST
  directory. FBL output NOD files are not used for event drive
  mail activities.

  When an Event Schedule declares "Mail" as part of the event,
  AceComm will scan the MAIL_OUT directory for *.FLO files.
  FLO type files supported are:

    FLO  ; file attach
    CLO  ; continuous
    DLO  ; direct
    OUT
    CUT
    DUT
    REQ  ; request

  AceComm will begin looking in the Nodelist directory for a
  NLIST.IDX file and associated NODELIST.nnn files. If found,
  AceComm will look up the target systems record, build a
  Fon.Record with the information, and begin dialing with
  intent to send mail, file requests etc. Any local systems
  will require a Dial filter statement be defined so that
  AceComm can translate the long distance number (as contained
  in the Nodelist) into a local one.

   The following dial statement filter "1-602-" from all phone
   numbers the  string is found in.
                  Dial filter 1-602-

   If a connection is established, and the mail file is
   properly processed (sent), upon success AceComm deletes the
   file. If the session for some reason is not successful
   (modems don't connect properly) and the file is not sent,
   AceComm will again scan the MAIL_OUT directory and process
   any mail files. AceComm scans the MAIL_OUT directory about
   every 30 minutes during a "Mail" event.

   File Requests .REQ files are considered mail files, and
   processed in the same way. During a "Mail" event. Files
   received during a file request are placed into the MAIL_IN
   directory.

   Filenames contained inside of FLO files, with exception to
   REQ files are to be sent out to the target system. Filenames
   that are prefixed with a '#' character are made ZERO length
   after sending. Filenames prefixed with '^' character are
   deleted upon successful send.


The following has been taken from the "Protocols" menus section.
Receive/Send Protocols sections present step by step through
File Request and File Attach.

--Recv Mail / File Request--
  "FileRequest" is a point mail function.
  Selecting File Request function will bring up the menu below
  if the PRM-data directory field for NODELIST points to either
    - FIDONET NODELIST and compiled NLIST.IDX file
    - FBL.EXE output .NOD file
  FBL output .NOD file is used in the example below.

 ╔═══════════════════════════════════════╗
 ║           1:114/12                   ║
 ║ Format =>  ZONE:NET/NODE              ║
 ╚═══════════════════════════════════════╝
 This menu prompts the user for a ZONE:NET/NODE number of the
 system we want to call. Having entered the above "1:114/12"
 the menu below is presented.

-- Send Mail / File Attach--
  This selection allows the user to send files to EMSI capable
  mailer software.  The menu shown below prompts the user for a
  FIDONET style ZONE:NET/NODE number.


┌─AutoAnswer Mode Setup─────────────────────────────────────────
│─Answer/Connect - Associated macro stack───────────────────────
│ CONNECT
│<RunProg>DSZ port %P speed %B sz ace.exe %WK
│─Answer/Connect - Associated macro stack───────────────────────
│ FAX
│ <RunProg>BGFAX /FAX %P %B
│─Answer/Connect - Associated macro stack───────────────────────
│
│
│─Default macro stack───────────────────────────────────────────
│ <RunProg>TRIBBS port %P speed %B minutes 45
└─── Edit  Quit  Help ┤<>├────────────────────────────────────

o AceComm will process a macro stack based on the
  Answer/Connect string

o Auto Answer mode can be toggled "On/Off" using a key press
assigned the <AutoAnswer> macro (ALT-E default)

o Auto Answer can be an EVENT, see "Event Scheduler" menu

Answer/Connect
   The sub-string will be looked for in the actual modem
   response string upon Answer/Connect

Associated macro stack
   Macro stack will be processed on "sub-string" found

Default macro stack
   Macro stack to process when sub-string search fails



┌─Event Schedules───────────────────────────────────────────────
│ Event 00:01-00:03,Mail
│Macro <ChgDir>c:\mail\qm <RunProg>QM scan <ChgDir>[DIR_START]
│ Event 8:30-9:0,Mail,Host
│ Macro <ChgDir>c:\mail\qm <RunProg>QM toss <ChgDir>[DIR_START]
│ Event
│ Macro
│ Event
│ Macro
│ Event
│ Macro
└─── Edit  Quit  Help ┤<>├────────────────────────────────────

AceComm will watch the clock for any event start times. When an
event rolls around the associated macro stack, if any will be
processed.

"Mail" events tell AceComm that it is ok to process any *.FLO
files contained inside the "MAIL_OUT" directory.

"Host" events tell AceComm it is ok to Auto Answer the line
when RING is detected. AceComm uses the UART RING bit and modem
status change for detecting RING.

see Auto Answer Setups for more information about Auto Answer



o  "Mondo Menus" are user definable menus

o  "Mondo Menus" can be used to group similar macro stacks
   together into one menu

o  "Mondo Menus" can be assigned to a hot key

Master "Mondo"
   Below is the "Mondo Menu" Master menu.  (macro is <Mondos>) A
   key-press may be assigned the <Mondos> macro as a hot key for
   this menu.  It lists five "Mondo" style menus available.

   Each "Mondo Menu" can be assigned a hot key.

F10 =  │ File │ Setup │ Phone │ Transfer │ Mondos │ Help │
                                         ┌─│──────────────────────┐
                                         │1  CIS Functions       │
                                         │ 2  OffLine Reader      │
                                         │ 3  Mondo Menu #3       │
                                         │ 4  Mondo Menu #4       │
                                         │ 5  Mondo Menu #5       │
                                         └─── Select  Quit  Help ─┘
   Here the first two menus have been given titles.  The titles
   were entered from the setup menu discussed later on.

   The following macros can be used for the five "Mondo Menus".
      <Mondo1>
      <Mondo2>
      <Mondo3>
      <Mondo4>
      <Mondo5>

   If I want to assign a hot key to the "Mondo Menu" labeled "CIS
   Functions" I can go into the PRM-data area "Key Setup" menus
   and assign a key press to the <Mondo1> macro.

   Example:  F11 <Mondo1>



A "Mondo Menu"

   Below is a "Mondo Menu".  This one was created by the author
   of AceComm as an example.  I came up with the idea for "Mondo
   Menus" a week before the 1.75 release, and so hadn't had time
   to document many tried-true Mondo setups.  The menus were
   designed to offer a means for grouping common macro stacks
   into menus.  I wanted to be able to create, change menus and
   menu items at will, as my on line needs changed.  "Mondo
   Menus" allow this sort of configuration flexibility.

   Each "Mondo Menu" has a title and seven function slots.

F10 =  │ File │ Setup │ Phone │ Transfer │ Mondos │ Help │
                                           ┌─CIS Functions─────────┐
                                           │CIS Forums Script     │
                                           │ CIS Bill Script       │
                                           │ Compose Message       │
                                           │ IBMPRO Forum 2 File   │
                                           │ IBMCOM Forum 2 File   │
                                           │                       │
                                           │ CIS Msg Reference     │
                                           └─(Select) Edit  Quit ──┘



Setup "Mondo"

   Below is the Setup menu for creating "Mondo Menus".

┌─"Mondo Menus" (Tm)────────────────────────────────────────────
│─Title field───────────────────────────────────────────────────
│- CIS Functions
│─Description / Associated macro stack pairs────────────────────
│ / CIS Forums Script
│ \ <RunScript>cisforum.scr
│ / CIS Bill Script
│ \ <RunScript>cisbill.scr
│ / Compose Message
│ \ <SendAscii>%P
│ / IBMPRO Forum 2 File
│ \ <SendStr>go IbmPro^M <OpenCapture>ibmpro <SendStr>Read New^M
│ / IBMCOM Forum 2 File
│ \ <SendStr>go IbmCom^M <OpenCapture>ibmcom <SendStr>Read New^M
│ /
│ \
│ / CIS Msg Reference
│ \ <RunProg>List cis_msg.ref
└───(Edit) Quit  Help ┤<>v^├────────────────────────────────────

Title field

   The Title field is 15 characters long, this will be the
   title that appears in you "Mondo Menu".

Description / Associated macro stack pairs

   "Description" fields are 20 characters, these will become the
   menu choices displayed from your "Mondo Menu".

   "Associated macro stack" fields are 80 characters, these are
   the actions that take place when you select a "Description"
   choice.

Support for a pointer device has been implemented into AceComm
using the Microsoft Mouse Driver functions. Your Microsoft
compatible mouse should work with AceComm.

-- Mouse in Terminal Area --

o Pressing the left mouse button sends <CR>

o Pressing right mouse button sends the character the mouse
  cursor is highlighting.


From Terminal Area, a one line mouse menu is presented on the top
row of the screen.  This menu presents several of the more
commonly used MACRO functions otherwise available from the
Terminal Area with a key press.

Placing the mouse cursor over a menu choice and pressing the left
button selects the menu item.

The menu can be toggled off from the PRM-data Terminal Options
menu.

The mouse can be used for Character I/O with the HOST.  The left
button sends <CR> character.  The right button sends the current
highlighted character.


-- Mouse in Menu Areas --

o Pressing the left button selects an item.

o Pressing the right button is the same as <ESC> or Quit

   Horizontal and vertical sensitivity can be adjusted from
   inside the PRM-data general controls menu.

   The mouse detection can be toggled "OFF" from inside the
   PRM-data General Controls menu.
   Turning "OFF" mouse detection completely disables AceComm
   from any mouse function related use, including Terminal Area
   mouse menu.



o   MACROS are directives bounded inside of angle brackets < >
o   MACROS must have a SPACE character in front of them when not
    the first command on a line.

 <ChgDir>[DIR_MAIL] <RunProg>BWAVE <ChgDir>[DIR_START]
                   |                 |
                   |_________________|
                   |
                   Leading space

o   MACROS may be any combination of CaSe

 <RunProgram> jmodem
 <runprogram> jmodem

o   The MACRO PROCESSOR supports MACRO STACKING
    MACRO STACKING means multiple MACROS per line

 <SendStr>u z ACE0601.ARJ^M <SendZmo>files\ace0601.arj
 <SendStr>u z ACE0601.ARJ^M <RunProg>DSZ sz -m files\ace0601.arj
 <SetDTR> ON <SendStr>ATDT846-2940^M <WaitStr>CONNECT <SendStr>^[^[


o   MACRO DATA PARAMETERS are bounded inside of square
    brackets [ ]

o   MACRO DATA PARAMETERS need not have a <SP> character in front
    of them

o   MACRO DATA PARAMETERS must be upper CASE

 <SendStr>[USER_NAME]^MY^M[FON_REC_PWD]
          |          |    |
          |          |    Data Param (Fon.Record password field)
          |          |
          |          ^M translates into a <CR> (carriage return)
          |
          Data Param (IEMSI user name field)

 <SendStr>[USER_NAME]^M~~~~[PASSWORD]^M
 |        |          |  |  |
 |        |          |  |  IEMSI password field
 |        |          |  |
 |        |          |  One second delay (~ = 1/4 second delay)
 MACRO    |          |
          |          Control character representation for <CR>
          |
          MACRO DATA PARAMETER (IEMSI data)


o   MACRO FUNCTION PARAMETERS are prefixed with a % character

 <SendZmo> %PF
  |        |
  |        MACRO FUNCTION PARAMETER (prompt for filename)
  |
  Internal Zmodem sending unit

 <RunProgram>dsz port %P speed %B sz %PF %WK <SendStr>^M
                      |        |     |   |
                      |        |     |   |
                      |        |     |   MACRO FUNCTION PARAM
                      |        |     |   (wait for key press)
                      |        |     |
                      |        |     MACRO FUNCTION PARAM
                      |        |     (prompt for filename)
                      |        |
                      |        MACRO FUNCTION PARAM
                      |        (insert ascii baud)
                      |
                      MACRO FUNCTION PARAM
                      (insert ascii port)



LUI MACROS require local keyboard input, and so  are  not  suited
to un-attended scripts.
LUI MACROS contain a '_' underscore as the last character
inside the brackets.

<AutoScrGen_>

   Toggle AutoScrGen(tm) mode

   Toggle AutoScript Generation mode On/Off.  When "On" an
   extended status line will appear at the bottom of the TERMINAL
   screen.  At the far left of the extended status line will be
   the phrase "AutoScriptGen"


<BackBuffer_>

   Menu Area
   Enter Back Buffer Screen Area

   BackBuffer contains the last n lines of display that scrolled
   off the TERMINAL screen.  BackBuffer has a status line of it's
   own.  The status line contains such information as current
   line position into the buffer, total lines buffered, and some
   of the navigational keys are displayed.  Hold the ALT key down
   for the POP UP REFERENCE available for the BackBuffer area.


<CaptureFile_>

   Toggle Capture File
   Prompts for filename

   Capture will also prompt for append or overwrite.  Capture
   does absolutely NO filtering of any kind.  All data is
   recorded to file "as it comes in the port".  The AceComm
   package comes with separate utilities which can strip video
   control codes from files.  See also <OpenCapture> filename,
   <CloseCapture>

<CommandShell_>

   Enter Shell to Command Processor/ Operating System

   In most cases "Drop to DOS", if your DOS compatible operating
   system places it's name in the environment where AceComm can
   find it.  "Shell" is not hard wired to COMMAND.COM but the
   COMMAND PROCESSOR as found in the environmental data area.


   Notes: When SWAP is  "ON",  the  serial  port  is  effectively
          disabled  during  the  shell.   When  SWAP is "OFF" the
          serial port remains active and  any  incoming  data  is
          handled  properly,  unless  the  receive  buffer  wraps
          around.

<FileRequest_>
   Menu driven EMSI file request function.


<FonListDialer_>

   Menu Area
   Enter .FON List / Dialer

   Dial/.FON directory area.  While AceComm allows manual dialing
   from inside the TERMINAL area, it most convenient to dial from
   a record contained in one of the .FON files available for use
   from the DIAL area.


<FileLister_>

   Menu Area
   Enter File Lister

   Files lister inside AceComm provides a basic directory list
   function capable of changing directories and drives.
   File-marking, deletion, selection for appropriate
   file-utility, etc.  LISTFILES may be created.  ACE.BCH is a
   file created by the Tag feature inside the File Lister Area.
   files tagged will be listed inside ACE.BCH as CR LF terminated
   strings.  When selecting any of AceComm's internal batch
   capable sending protocols, AceComm will check for the existent
   of the file ACE.BCH and allow sending from the LISTFILE if
   desired.


<MdmHangUp_>

   Prompts Yes/no before,
   Sends PRM-data MDM_HANGUP string to modem.  Waits 1/2  second,
   then drops DTR for 1 second.

See also    <MdmHangUp> (non LUI)


<PrmDataMenus_>

   Menu Area
   Enter PRM-data Menu Area

   Notes: When AutoSave is "ON", all data changed is automatically
          saved when exiting the PRM-data area.


<RProtocols_>

   Menu Area
   Enter Receive Unit Protocols Area menu


<RunScript_>

   List .SCR directory, Allow selection, Run selected .SCR file

   Lists  the  PRM-data .SCR directory Allows selection of a .SCR
   file for immediate execution.

   Notes:  AceComm  allows  .SCR file as an argument when started
          which immediately executes the script.


<ScrnSnapShot_>

   Menu Area
   Take Screen Snapshot

   Create a "SnapShot" of the current screen minus any status
   lines active.  Prompts for a filename.  Filenames always will
   have the .SNA extension.  AceComm can detect and will strip
   away filename extensions provided by the user when they do not
   match that of the function.  This command is available from
   most ALT POP UP REFERENCE areas.


<ScrnTag_>

   Menu Area
   Enter Screen Tagger Screen Area

   Tagger will allow tagging to the first SPACE_CHAR or press
   RIGHT-ARROW Tagger tags the entire line of text.  Tagger has
   it's own status line, and a block cursor will appear inside of
   the Tagger mode.  Tagged items will be assigned to the next
   available SHIFT-Fn key.

   Tagger pops up the SHIFT-Fn key window and displays each
   tagged item, as they are tagged.  Tagger is most handy for
   grabbing filenames for download off a BBS screen.  SHIFT-Fn
   key fires the tagged item back when ready.  This command is
   available from most ALT POP UP REFERENCE areas.


<SProtocols_>

   Menu Area
   Enter Sending Unit Protocols Area


<ViewKeyCombos>

   Bring up Pop up Reference

   Note: <ViewKeyCombos> macro does not have the trailing '_'
         in the text

<TopBar>

   Activate the menu bar at top of screen

The following macros can be used to call individual menus
otherwise choices from the TopBar single line menu

<FileMenu>

   The TopBar File menu

<HelpMenu>

   The TopBar Help menu

<PhoneMenu>

   Calls the <FonListDialer_> macro

<SetupMenu>

   Calls the <PrmDataMenus_> macro

<XfrMenu>

   The TopBar Transfer menu



<DoorWayMode>

   Toggle doorway mode.  Saves the key press combo on entry,
   whatever key-combo you assign <DoorWayMode> to, is the only
   way out.  Doorway sends all key presses to the modem in their
   RAW 'un-cooked' form.  Non extended key presses are send LOW
   BYTE ONLY.  Extended key presses are sent LOW BYTE, HIGH BYTE.

<DispText> LABEL_NAME

   Display text defined in a data area of a script file
   LABEL_NAME is descriptive text following  {-TEXT_START-}
   Text is displayed at current cursor position
   Text display is local

------------snip here -------------
<ClearWindow>
<DispText>Intro
<DispText>Ask_Continue
:GetKey
<GetKey>
   <if>Y
   <goto>Dial
   <if>N
   <goto>End
   <goto>GetKey
:Dial
<INITFONREC>ACECOMM Support BBS      ; Initialize a FON RECORD
<FON_NUM>1-602-846-2940            ;
<FON_BAUD>19200                    ;
<FON_TERM>Av/An                    ;
<FON_REDIAL>                       ; Go into re dial mode
<DispText>Connect
<WAITSTR> your name:
<GetDCD>                           ; <WaitStr> may have timed
   <if>1                           ; out
   <goto>Connect
   <goto>Dial
:Connect
<SENDSTR>Michael Phelps^M
<SENDSTR>Y^M
<SENDSTR>password^M
<WAITSTR>Select:
<SENDSTR>ff
:End
<ENDS>


{-DATA_AREA-}
{-TEXT_START-}Intro
-- Generic Log On Script --
{-TEXT_END-}
{-TEXT_START-}Ask_Continue
Continue (Y/n) {-TEXT_END-}

{-TEXT_START-}Connect
-- Connect --
{-TEXT_END-}
------------snip here -------------


<HostEcho>

   Toggle Host echo mode.  This macro emulates HostMode's ECHO
   capability.  It does not answer the phone.  However modems set
   up for auto answer function normally.


<LocalEcho>'  ,0

   Toggle local character echo.  Local key-presses will be echoed
   to the screen.  (same effect as sending "ATE1^M" to the modem)


<SendStr> STRING

   Sends a string to the modem.

      <SendStr>^M
       Send a single CR_CHAR

      <SendStr>  Michael  Phelps^M
       Notes: the leading SPACE_CHAR part of STRING

      <SendStr>[USER_NAME]^M~~~~Y^M~~~~[FON_REC_PWD]
       Send IEMSI data user name field, a <CR> char, 1 second
       pause, Y, <CR> char, 1 second pause, current
       Fon.Record.Password.

      <SendStr>[USER_NAME]^M^M[PASSWORD]^M
       Send IEMSI data user name field, 2 <CR> chars, IEMSI
       data password field.


<WaitStr> STRING

   Waits for a CASE sensitive string (sequence of characters)  to
   come  in the from the modem.  Can TIMEOUT.

   Notes:  The  example  below contains a SPACE_CHAR as the first
          character of STRING.

          <WaitStr> name:

   Arguments  to  MACROS  are  taken  as  is,  up  until the first
   <CR> on the line of text.

   A normal text editor in ASCII TEXT mode will have placed the
   CR_CHAR as the byte following the ':' character in the example
   STRING below ' name:'.  File Functions internal to AceComm
   will filter the leading SPACE_CHAR from the MACRO ARG.


<WaitTime> n

   Where n is in seconds
   Set the timeout value for <WaitStr>




<SetFonFile> FILENAME

   Tacks  FILENAME  onto  the  PATH  defined in PRM DATA for .FON
   files.  AceComm keeps track of the current(last accessed) .FON
   file.  FILENAME becomes the current .FON  file.   <SetFonFile>
   1_114.fon <DialRecord> 1


<ChgDir> FILENAME

   Make FILENAME current directory


<FileDel> FILENAME

   If the file exists, it will be deledted without prompt.
   Use full path name if not in current directory.


<OpenCapture> filename

   Calling this function opens a capture file in the directory
   path defined inside PRM-data Area "Directories" menu, .CAP
   files. This function will first close an open capture file,
   properly saving it to disk.


<CloseCapture>

   Close the current open capture file, or just returns if none
   is open.
   Notes: capture files are automatically closed on detection
   of a loss in carrier.


<RunScript> FILENAME

   Open and run FILENAME

   Notes:  Just FILENAME no PATH.  PATH found in PRM-data as .SCR
           is used.


<RunProgram> FILENAME
<RunProg> FILENAME    <= short form for this macro

   Spawn an executable file.   Can  search  the  DOS  PATH.   Can
   determine files's extension (.COM, .EXE).  All system ISRs are
   restored  before  the  spawn  takes place.  The serial port is
   un-hooked.  The state of DCD, and LINE  CONTROL  are  left  in
   tact.

   After  the  spawn the system ISRs AceComm uses are taken back,
   the serial port is re-assumed.

   SWAP FLAG "ON" and XMS,EMS,  or  DISK  swapping  takes  place.
   SWAP  FLAG "OFF" and AceComm is left in memory, with exception
   to first restoring the serial port and interrupts.



<SendASCII> C:\MSG\COMM\ASCII.TX1

   Outputs from a file to the modem.  Sends  the  complete  file.
   Does  *NO*  CONTROL  CHARACTER  TRANSLATION.  Data sent to the
   modem is paced for buffer FULL, and all handshaking is valid.

   ESC-key press aborts the function.


<SendZmo> FILENAME

   Call internal zmodem sending unit with 1k data frame size.

   ESC-key press aborts the function.


<RecvZmo>

   Call internal zmodem recv  unit.   AceComm's  internal  zmodem
   receiver  is capable of up to 8k data frame size.  The receive
   unit will continue  in  batch  mode  until  the  sender  stops
   sending files, or the user terminates the transfer.  Files are
   placed  into the directory pointed to in the PRM-data area for
   Downloads.

   ESC-key press aborts the function.


<SendYmo> FILENAME

   Call internal ymodem sending unit with  128  byte  data  frame
   size.

   ESC-key press aborts the function.


<SendYmo1k> FILENAME

   Call internal ymodem sending unit with 1k data frame size.

   ESC-key press aborts the function.


<SendYmoG> FILENAME

   Call internal ymodemG sending unit with 1k data frame size.

   ESC-key press aborts the function.


<SendXmo> FILENAME

   Call  internal  xmodem  sending  unit with 128 byte data frame
   size.

   ESC-key press aborts the function.


<SendXmo1k> FILENAME

   Call internal xmodem sending unit with 1k data frame size.

   ESC-key press aborts the function.


<RecvYmo>

   Call internal ymodem.  The receive unit will continue in batch
   mode until  the  sender  stops  sending  files,  or  the  user
   terminates  the transfer.  Files are placed into the directory
   pointed to in the PRM-data area for Downloads.

   ESC-key press aborts the function.

<RecvYmo1K>

   Call internal ymodem1K.  The receive  unit  will  continue  in
   batch  mode  until the sender stops sending files, or the user
   terminates the transfer.  Files are placed into the  directory
   pointed to in the PRM-data area for Downloads.

   ESC-key press aborts the function.


<RecvYmoG>

   Call  internal  ymodemG.   The  receive  unit will continue in
   batch mode until the sender stops sending files, or  the  user
   terminates  the transfer.  Files are placed into the directory
   pointed to in the PRM-data area for Downloads.

   ESC-key press aborts the function.


<RecvXmo> FILENAME

   Call internal xmodem.  Files are  placed  into  the  directory
   pointed to in the PRM-data area for Downloads.

   ESC-key press aborts the function.

<RecvXmo1K> FILENAME

   Call  internal  xmodem1k.  Files are placed into the directory
   pointed to in the PRM-data area for Downloads.

   ESC-key press aborts the function.


<SendEMSI_CLI>

   Send an EMSI_CLI HDR sequence to modem

   BBS  mailer  front ends that use EMSI handshake protocol will,
   if EMSI is implemented properly, interpret an  "EMSI_CLI"  HDR
   sequence,  as  "this  is  a  human caller" and drop to the BBS
   without any delay.  Note: At  this  writing  Front  Door,  and
   Binkley  recognize  EMSI_CLI  HDR.   DBridge  does  not.   See
   default AutoD trigger assignments (ACE.CTL)


<SendEMSI_ICI>

   Send an EMSI_ICI data packet to modem

   EMSI_ICI is a response made by the caller (CLIENT)  to  a  BBS
   system   (HOST)  which  supports  Interactive  EMSI  handshake
   protocol.  IEMSI data is contained inside the  PRM-data  area.
   This  data  can  be used for automating log on when call a BBS
   that supports IEMSI.  See default  AutoD  trigger  assignments
   (ACE.CTL)



Notes: Xmodem/Ymodem Receive units are capable of adopting to
       frame size.  128 / 1024 data frames are determined by the
       sender and can be sent in any combination.

       The Internal Zmodem in AceComm is capable of up to 8k data
       frames.  For compatibility, AceComm only uses larger than
       1k data frames with it's sending unit in mailer modes.
       AceComm's zmodem receive unit can handle up to 8k data
       frames at any time.




<AutoAnswer> On
<AutoAnswer> Off

   PRM-data MDM_HOST_INIT is sent to the modem when hostmode flag
   is toggle "ON".  PRM-data MDM_INIT is sent to the modem when
   hostmode flag is toggled "OFF".  AceComm begins responding to
   the RI bit SET, and will send the MDM_ANSWER string to the
   modem when RI BIT becomes asserted.  <HostEcho> becomes
   active.
   Upon Answer/Connect an attempt to match modem response string
   those defined in the Auto Answer Setup menu.

   Notes: Auto Answer is also terminated whenever the user dials
          out from the FON LIST MENU AREA.

   See your modems S7 register as an alternative.

See also   Auto Answer Setup menu


<DialNum> PHONE_NUMBER

   Builds a  dial  string.   Uses  PRM-data  MDM_DIAL_PREFIX  and
   PHONE_NUMBER  Sends  the  dial string to the modem.  One time.
   No re dials


<DialRecord> n

   Retrieves the n record found in current .FON file

   Re dials number until CONNECT or USER ABORT

       <SetFonFile> 1_114.FON <DIALRECORD> 1


<GetDCD>

   Returns 0 or 1 current carrier detect signal


<MdmHangUp>

   Sends PRM-data MDM_HANGUP string to modem.  Waits 1/2  second,
   then drops DTR for 1 second.


<SetDTR> ON/OFF

   SET or RESET UART BIT

        <SetDtr> OFF

-------------------------
Build a Fon.Record macros
-------------------------

<InitFonRec> RECORD NAME

   This  MACRO must be called first.  The MACRO initializes a FON
   RECORD with AceComm defaults.  RECORD NAME is copied into  the
   system name for this record.

      <InitFonRec> Compuserve


<Fon_Num> PHONE_NUMBER

   Set  the  phone  number field.  Any dial statements in ACE.CFG
   will be applied to this number when AceComm  builds  the  dial
   string.

      <Fon_Num>468-0285


<Fon_Baud>BAUD

   If  using  a  locked port, AceComm will ignore this value when
   getting ready to dial.

      <Fon_Baud>19200


<Fon_LineCtrl> DATA_PARITY_STOPBIT

   Valid parameters are as follows
         8n1
         7e1
         7n1

      <Fon_LineCtrl>8n1


<Fon_Flags> FLAG, FLAG

   Possible Control Flags

   "Script" when set,
   AceComm will attempt to load and run the filename defined next
   to "AutoLogOn Script".  If a script file is not found, AceComm
   ignores the error and continues normal operation.

   Notes: .SCR files are looked for in the directory defined
           inside PRM-data Area "Directories"

   "Macro"  when  set,
   AceComm will enable the defined Auto Log on Sequence Triggers
   and corresponding MACRO stacks.

   "DTag"  when  set,
   AceComm will tag un-successful dial attempts (busy, etc.) to
   the Que Dialer.  An "*" character appears to the left of a
   Fon.Record's display line, when it is either Q tagged or, D
   tagged.  When this flag is not set, the only other way to Q
   tag a record is by manually selecting the menu option
   "<SPACEBAR>-Que" from the fon list display.

   "Capture" when  set,
   When this flag is selected, a capture file is opened upon
   Dial/Connect.  Any previously open capture file is first
   closed.

   "Raw"  when set,
   Data to capture file is as it comes in from the modem

   "Text"  when set,
   Data to capture file is filtered of video control codes
   as appilcable to the current Video type

   "IEMSI"  when  set,
   Allow Interactive EMSI log on

  "AutoL"
  Allow auto log on methods (script/macro)


<Fon_Term> VIDEO_TYPE

      - Valid parameters are as follows

        TTY
        Ansi
        Avatar
        Av/An
        VT102

      <Fon_Term>Av/An


<Fon_CapFile> FILENAME


<Fon_Redial>

   Presents the FON record to the AceComm re dial function.



<ClearWindow>

   Clear screen. Clears screen above status line


<Delay> SECONDS

   Create program function delay.


<EndAceComm> ERRORLEVEL

   <EndAceComm> 0
   AceComm session end.

   Exit AceComm  back  to  the  operating  system.   End  AceComm
   session.   A QUICK snap, no prompt "Are you sure?".  If your on
   line, your still on line when you come back unless  "drop  DTR
   on exit is SET"

   See Drop DTR on EXIT flag inside Terminal Area Options

<BbsEndAceComm>

   This macro will Exit AceComm with an errorlevel based on the
   current baud setting. Baud is taken from the UART, and if
   the port is locked, will vary from the connect speed.
   Errorlevel equale the first 2 digits of the current UART
   baud setting.
   DTR state is left as is.
   Errorlevels returned are:
                             57 - 57600
                             38 - 38400
                             19 - 19200
                             96 -  9600
                             48 -  4800
                             24 -  2400
                             12 -  1200
                             30 -   300
   Sample use:
:Start
   echo off
   ace
   if errorlevel 96 goto error96
   if errorlevel 57 goto error57
   if errorlevel 48 goto error48
   if errorlevel 38 goto error38
   if errorlevel 24 goto error24
   if errorlevel 19 goto error19
   goto start
:error57
   BBS.EXE 57600
   goto Start
:error38
   BBS.EXE 38400
   goto Start
:error19
   BBS.EXE 19200
   goto Start
:error96
   BBS.EXE 9600
   goto Start
:error48
   BBS.EXE 4800
   goto Start
:error24
   BBS.EXE 2400
   goto Start
:error12
   BBS.EXE 1200
   goto Start
:End


<RingBell> SECONDS

   A value of 0 does not ring bell, a value of 1 plays a
   victory tune, values from 2 - 30 ring the internal bell for
   the number of seconds. This is the same bell sound heard in
   the Dial/Connect window.



<Wait_To_HHMM> hh:mm

   Wait until hour:minute     24 hour format
   leading zeros not needed

           <Wait_To_HHMM>4:10    is valid

   Sample use:

    <Wait_To_HHMM>15:45                ; wait till 3:45 pm
    <INITFONREC>A.C.E. Software Support; call Init FON function
    <FON_NUM>1-602-846-2940            ; set phone number
    <FON_BAUD>2400
    <FON_TERM>Av/An                    ; video type for script
    <FON_REDIAL>                       ; call redial function
    <WAITSTR>it a few moments.

    <SENDSTR>^M
    <WAITSTR>s your name:
    <SENDSTR>Michael Phelps^M
    <WAITSTR>ael Phelps [Y,n]?
    <SENDSTR>^M
    <WAITSTR>Password:
    <SENDSTR>melissa_jean^M
    <WAITSTR>Select:
    <SENDSTR>f^M
    <SENDSTR>d^Mz^Mace170.arj^M
    <RecvZmo>
    <WAITSTR>Select:
    <SENDSTR>gyn^M
    <ENDS>
    <ENDS>

   Mark the end of a script.


o MACRO parameters are UPPER case only

The following are data from Fon.Records


[FON_REC_PWD]

   Replaced with the current FON RECORD'S "password"


[FON_REC_CAP]

   Replaced with the current FON RECORD'S CAPTURE "filename"


[FON_REC_SCR]

   Replaced with the current FON RECORD'S SCRIPT "filename"

The following are data from PRM-data IEMSI section


[USER_NAME]

   Replaced with the current PRM-data/IEMSI "User Name"

      <SendStr> [USER_NAME]


[ALIAS]

   Replaced with the current PRM-data/IEMSI "alias"


[LOCATION]

   Replaced with the current PRM-data/IEMSI "location"


[DATA_PNUM]

   Replaced with the current PRM-data/IEMSI "data #"


[VOICE_PNUM]

   Replaced with the current PRM-data/IEMSI "voice #"

[PASSWORD]

   Replaced with the current PRM-data/IEMSI "password"


The following are data from PRM-data DIRECTORY section


[DIR_START]

   Replaced with the current PRM-data/DIR "start up"
   This is the directory AceComm is started in.


[DIR_FON]

   Replaced with the current PRM-data/DIR ".FON"


[DIR_CAP]

   Replaced with the current PRM-data/DIR ".CAP"


[DIR_SCR]

   Replaced with the current PRM-data/DIR ".SCR"


[DIR_KTS]

   Replaced with the current PRM-data/DIR ".KTS"


[DIR_DNLDS]

   Replaced with the current PRM-data/DIR "dnlds"

<ChgDir> [DIR_DNLDS] <RunProgram>DSZ rz -mr <ChgDir> [DIR_START]


[DIR_NODELIST]

   Replaced with the current PRM-data/DIR "nodelist"


[DIR_MAILIN]

   Replaced with the current PRM-data/DIR "mail_in"

[DIR_MAILOUT]

   Replaced with the current PRM-data/DIR "mail_out"


The following are data from PRM-data MODEM section


[MDM_INIT]

   Replaced with the current PRM-data/MDM "init"


[DIAL_PREFIX]

   Replaced with the current PRM-data/MDM "dial prefix"


[DIAL_SUFFIX]

   Replaced with the current PRM-data/MDM "dial suffix"


[ANSWER]

   Replaced with the current PRM-data/MDM "answer"


[HANGUP]

   Replaced with the current PRM-data/MDM "hangup"


[OFFHOOK]

   Replaced with the current PRM-data/MDM "off hook"


[ABORT]

   Replaced with the current PRM-data/MDM "abort"


[RESET]

   Replaced with the current PRM-data/MDM "reset"


[ECHO]

   Replaced with the current PRM-data/MDM "echo"


[HOST_INIT]

   Replaced with the current PRM-data/MDM "host init"


[CMD_LINE_TERMINATOR]

   Replaced   with   the   current   PRM-data/MDM  "command  line
   terminator"



o  Expandable MACRO Functions are UPPER case only

%B
   Insert ascii baud, %B is replaced with current baud setting
   in ascii format.
   Current baud setting is UART line speed, if the port is
   locked, this will differ from the modem connect speed.

%P
   Insert ascii port, %P is replaced with current port number
   is ascii format. Port number is 1 based (com1 =1, com2 =2)

%FN   (Valid when used from <FileLister_>)

   Use from File Lister  Area,  %FN  is  replaced  with  currently
   "highlighted" filename.

%PF
   Prompt  for  filename,  %PF is replaced with what you type into
   the prompt box.

%WK

   Wait for Key press, stops MACRO execution and waits for a  key
   press.



AceComm generates script files automatically when running in
AutoScriptGen mode.  The macro <AutoScrGen_> puts AceComm into
AutoScriptGen mode.  AceComm default keyboard file ACE_DEF.KBD
assigns ALT-A to <AutoScrGen_>.


AutoScriptGen first prompts for a filename to use for the script
file.  The extension .SCR will automatically be appended.

╔═Input Window══════════════════════════════════════════════════
║═Enter filename, <ENTER> alone when done, ESC-abort════════════
║=> D:\ACE\CSERVE░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
╚═══════════════════════════════════════════════════════════════

Having a filename, AutoScriptGen creates the file and waits for
activity. We want to call out. Lets bring up the FON directory
and select Compuserve.

╔═ Telephone_directory fon\ACE.FON, 9 Records═══════════════════
║═      System Name              Phone Number     Line Control V
║ 1    AceComm Support BBS      1-602-846-2940     19200,8N1   A
║2    CIS (local phoenix 9600) 468-0285           19200,7E1   A
║ 3    CIS (phones)             1-800-346-3247     2400,7E1    A
║ 4    Comp USA #2              1-214-620-7993     19200,8N1   A
║ 5    Supra Modem BBS          1-503-967-2444     19200,8N1   A
║ 6   Comput Connections (PCB) 1-202-547-2008     19200,8N1   A
║ 7   Comp USE (Dallas TX)     1-214-620-2255     19200,8N1   A
║  Dial  Edit  <SPACEBAR>-Que  Circling_dial_queue  Fon_files  S
╚═ Add_record  Remove_record  UnMark_All  Import  Paint  Quit  H

AutoScripGen will write Fon.Record information to the script
file in the form of macro commands.
Below is a simple script file produced by AutoScriptGen. The
first 5 lines are a result of having selected a Fon.Record to
dial from inside the dialing area. AutoScriptGen has used 4
macro commands to initialize a Fon.Record and a 5'th macro to
call the continuous dialer function.

FILE: CSERVE.SCR

------------snip here -------------
<INITFONREC>CIS (local phoenix 9600)
<FON_NUM>468-0285
<FON_BAUD>19200
<FON_TERM>Av/An
<FON_REDIAL>
<SENDSTR>^M
<WAITSTR>Host Name:
<SENDSTR>cis^M
<WAITSTR>User ID:
<SENDSTR>75120,3306^M
<WAITSTR>Password:
<SENDSTR>cis/pwd^M
<WAITSTR>er choice number !
<SENDSTR>go ibmpro^M
<WAITSTR>Press <CR> !
<SENDSTR>^M
<OPENCAPTURE>ibmpro
<WAITSTR>Enter choice !
<SENDSTR>READ NEW^M
<WAITSTR>ress <CR> !
<SENDSTR>^M
<CLOSECAPTURE>
<WAITSTR>Enter choice !
<SENDSTR>off^M
<WAITSTR>Host Name:
<SENDSTR>off^M
<ENDS>
------------snip here -------------

The following example has been used by the author successfully
(remember to insert your password)
Example CIS Billing
------------snip here -------------
<ClearWindow>
<DispText>Intro
<INITFONREC>CIS (local phoenix 9600)
<FON_NUM>468-0285
<FON_LINECTRL>7E1
<FON_BAUD>19200
<FON_TERM>Av/An
<FON_FLAGS>Macro,IEMSI,
<FON_REDIAL>
<LocalKeys>On
<WaitTime>10
<SENDSTR>^M
<SENDSTR>^M
<WAITSTR>Host Name: <SENDSTR>cis^M
<WAITSTR>User ID: <SENDSTR>75120,3306^M
<WAITSTR>Password: <SENDSTR>password/here^M
<WaitTime>20
<WAITSTR>choice number ! <SENDSTR>2^M
<WAITSTR><CR> for more ! <SENDSTR>8^M
<WAITSTR>Enter choice ! <SENDSTR>2^M
<WAITSTR>Enter Choice ! <SENDSTR>2^M <OPENCAPTURE>CISBILL.CAP
<WAITSTR><CR> for more ! <SENDSTR>^M
<WAITSTR>Last page ! <SENDSTR>^M
<WAITSTR>Enter Choice ! <SENDSTR>3^M
<WAITSTR><CR> for More ! <SENDSTR>^M
<WAITSTR>Last Page ! <SENDSTR>^M
<WAITSTR>Enter Choice ! <SENDSTR>4^M
<WAITSTR>Last Page ! <SENDSTR>^M
<WAITSTR>Enter Choice ! <CLOSECAPTURE> <SENDSTR>off^M
<WAITSTR>Host Name: <SENDSTR>off^M
<ENDS>
{-DATA_AREA-}
{-TEXT_START-}Intro
-- Compuserve Billing Information --

   This script captures the current months charges, and a review of
   the last svereal months billing to a capture file "CISBILL.CAP"
   The script then logs off. The script could be interupted if you
   have CIS configured to display mail and other anouncements on
   login.

{-TEXT_END-}
------------snip here -------------


The following example has been used by the author successfully
(remember to insert your password)
Example CIS Forums
------------snip here -------------
<ClearWindow>
<DispText>Intro
<INITFONREC>CIS (local phoenix 9600)
<FON_NUM>468-0285
<FON_LINECTRL>7E1
<FON_BAUD>19200
<FON_TERM>Av/An
<FON_REDIAL>
<SENDSTR>~~~~~~~~~^M
<WAITSTR>Host Name: <SENDSTR>cis^M
<WAITSTR>User ID: <SENDSTR>75120,3306^M
<WAITSTR>Password: <SENDSTR>password/here^M

<WAITSTR>er choice number ! <SENDSTR>go share^M
<WAITSTR>Press <CR> ! <SENDSTR>^M
<WAITSTR>Enter choice ! <OPENCAPTURE>share <SENDSTR>READ NEW^M
<WaitTime>500 <WAITSTR>ress <CR> ! <SENDSTR>^M
<WAITSTR>Enter choice ! <CLOSECAPTURE>

<SENDSTR>go ibmcom^M
<WAITSTR>Press <CR> ! <SENDSTR>^M
<WAITSTR>Enter choice ! <OPENCAPTURE>ibmcom <SENDSTR>READ NEW^M
<WaitTime>500 <WAITSTR>ress <CR> ! <SENDSTR>^M
<WAITSTR>Enter choice ! <CLOSECAPTURE>

<SENDSTR>go ibmpro^M
<WAITSTR>Press <CR> ! <SENDSTR>^M
<WAITSTR>Enter choice ! <OPENCAPTURE>ibmpro <SENDSTR>READ NEW^M
<WaitTime>500 <WAITSTR>ress <CR> ! <SENDSTR>^M
<WAITSTR>Enter choice ! <CLOSECAPTURE>

<SENDSTR>off^M
<WAITSTR>Host Name:
<SENDSTR>off^M
<ENDS>
{-DATA_AREA-}
{-TEXT_START-}Intro
-- Compuserve Forums --

   This script captures the new messages for 3 forums. SHARE, IBMCOM,
   and IBMPRO. The forums are captured to 3 separate files. SHARE.CAP,
   IBMCOM.CAP, and IBMPRO.CAP.
   The script then logs off. The script could be interupted if you
   have CIS configured to display mail and other anouncements on
   login.

{-TEXT_END-}
------------snip here -------------






         :Label
            Labels begin with ':' character
            Labels are used as arguments to the <goto> macro

         <goto> label
            "Label"  can be defined any where in the script file, either
            before or after a <goto> macro.

         <if> condition
            AceComm supports a set of conditional macros. Conditional
            macros return either 1 or 0.

         {-DATA_AREA-}
            Defines a data area

         {-TEXT_START-}
          see examples
         {-TEXT_END-}


            {-Data_ Area-} will be covered extensively next month with
            many complex scripts as well as complete documentation.

            The following script introduces some un-documented script
            language features.


            Follows is a basic script which includes a data area.

         ------------snip here -------------
         <ClearWindow>
         <DispText>Intro
         <DispText>Ask_Continue
         :GetKey
         <GetKey>
            <if>Y
            <goto>Dial
            <if>N
            <goto>End
            <goto>GetKey
         :Dial
         <INITFONREC>ACECOMM Support BBS      ; Initialize a FON RECORD
         <FON_NUM>1-602-846-2940            ;
         <FON_BAUD>19200                    ;
         <FON_TERM>Av/An                    ;
         <FON_REDIAL>                       ; Go into re dial mode
         <DispText>Connect
         <WAITSTR> your name:
         <GetDCD>                           ; <WaitStr> may have timed
            <if>1                           ; out
            <goto>Connect
            <goto>Dial
         :Connect
         <SENDSTR>Michael Phelps^M
         <SENDSTR>Y^M
         <SENDSTR>password^M
         <WAITSTR>Select:
         <SENDSTR>ff
         :End
         <ENDS>


         {-DATA_AREA-}
         {-TEXT_START-}Intro
         -- Generic Log On Script --
         {-TEXT_END-}
         {-TEXT_START-}Ask_Continue
         Continue (Y/n) {-TEXT_END-}

         {-TEXT_START-}Connect
         -- Connect --
         {-TEXT_END-}
         ------------snip here -------------



------------snip here -------------
    <Wait_To_HHMM>15:45                ; wait till 3:45 pm
    <INITFONREC>A.C.E. Software Support; call Init FON function
    <FON_NUM>1-602-846-2940            ; set phone number
    <FON_BAUD>2400
    <FON_TERM>Av/An                    ; video type for script
    <FON_REDIAL>                       ; call redial function
    <WAITSTR>it a few moments.

    <SENDSTR>^M
    <WAITSTR>s your name:
    <SENDSTR>Michael Phelps^M
    <WAITSTR>ael Phelps [Y,n]?
    <SENDSTR>^M
    <WAITSTR>Password:
    <SENDSTR>melissa_jean^M
    <WAITSTR>Select:
    <SENDSTR>f^M
    <SENDSTR>d^Mz^Mace170.arj^M
    <RecvZmo>
    <WAITSTR>Select:
    <SENDSTR>gyn^M
    <ENDS>
    <ENDS>
------------snip here -------------


             AceComm (Tm) Version  1.75

AceComm is distributed to you as "Try before you buy" software.

Continued use of the AceComm package requires the registration
fee be sent to the author.

Registering AceComm gives you access to one of the more powerful
and innovative communications programs available.

AceComm registration costs just $45. (includes shipping)
You will receive an up-to-date printed bound user manual, the
very latest AceComm software on disk, your registration card and
serial number, 1 FREE upgrade card, major revision upgrade
notices mailed to you, all future upgrades at very low cost of
20% registration fee.
    (Wow, major upgrades include printed manual for just $9)
To place an order, please use the order form contained in the
file ACEORDER.FRM, or print directly from the program Help menu.

        800-242-4775  (Toll free) To register by credit card.
        FAX at 713-524-6398
        Part number 10805



                    AceComm & Utilities (Tm)
                         Version  1.75
                          ORDER FORM



FROM:

     Name: ____________________________________________________

[Company]: ____________________________________________________

  [Title]: ____________________________________________________

  Address: ____________________________________________________

     City: ____________________________________________________

    State: ___________________________ Zip Code: ______________

  Country: ___________________________ Phone: _________________





                                   TO:
                                       AceComm Software
                                       3003 N. Central Ave. #121-171
                                       Phoenix, AZ    85012   USA


              ┌─────────┐
        ┌─────┴───┐     │              (R)
      ──│         │o    │──────────────────
        │   ┌─────┴╨──┐ │  Association of
        │   │         │─┘  Shareware
        └───│    o    │    Professionals
      ──────│    ║    │────────────────────
            └────╨────┘    MEMBER




                    AceComm & Utilities (Tm)
                         Version  1.75
                          ORDER FORM

Telephone   (602) 846-4563     AceComm Support Services
AceComm BBS (602) 846-2940     3003 N. Central Ave Suite 121-171
CompuServe  75120,3306         Phoenix, AZ  85012  USA
================================================================
Individual Registration Licensing use of AceComm and Utilities

- commercial version software  & documentation on diskette
- printed bound manual, upgrade notices)
- 1 upgrade sent FREE (you choose the version)
- all future upgrades at very low cost of 20%
  1'st FREE & all future upgrades include disk/printed manual

for MS-DOS:   1 Purchase at $45 (includes shipping) . . . ______
================================================================
INTERNAL SITE LICENSE for the use of AceComm & Utilities for DOS

- commercial version software  & documentation on diskette
- 1 upgrade sent FREE (you choose the version)
- all future upgrades at very low cost of 20%

  Quantity Registrations
  ----------------------
     10 - 50 ..         at $32 each, nbr computers ___x 32 _____
     50+                call for special discount
     custom features available
     call for quantity manual pricing
================================================================
Overseas add $7.00/order  for shipping and handling        _____

Diskette format (choose one)  5.25" disk (__)  3.5" disk (__)
================================================================
TOTAL PRODUCTS                                             _____

 Sales tax for Arizona residents                   6.5%    _____

TOTAL ORDER                                                _____

For payment by non-USA BANK CHECK, add $40.00              _____

Payment method:                            TOTAL ENCLOSED  _____
           ( ) Check           ( ) Cash
           ( ) Money order
           ( ) Credit card - See instructions in file CREDIT.CRD





                    AceComm & Utilities (Tm)
                         Version  1.75
                    Credit Card Order Form








     As a service to AceComm customers who want to register by  credit
     card,  arrangements  have  been  made  with  the  Public Software
     Library (PSL) to  handle  all  credit  card  registrations.   PSL
     accepts Visa, MasterCard, American Express, and Discover Card.

     Non-U.S.   residents  are  encouraged to register by credit card.
     In many  cases,  paying  by  credit  card  will  be  easier  than
     acquiring U.S.  funds.

     PSL will take the order information and forward it to the AceComm
     author,   MGP   Programming  Services  &  Michael  G  Phelps  for
     processing and shipping.



                    AceComm & Utilities (Tm)
                         Version  1.75
          AceComm Software Credit Card Registration Form
                    PSL Part number 10805




     The PSL part number for AceComm is: 10805

     Credit card registrations may be made by the following methods:

     -- Phone PSL at:
        800-242-4775  (Toll free) To register by credit card.
        713-524-6394  To  register  by  credit  card  and  for   order
                      inquiries.

     Be sure to have BOTH the credit card form at the end of this file
     PLUS the order form in the file ORDERFRM.DOC  available  to  give
     order information to PSL.

     ACCURACY in phone ordering is important!  Misspellings can result
     in delays or an erroneous registration.

     -- FAX PSL at 713-524-6398

     -- Email PSL at CompuServe user id 71355,470

     -- Write PSL at:
        The Public (Software) Library
        P.O. Box 35705
        Houston, TX 77235-5705
        USA
        PSL Part number 10805

     For FAX, email, or mail to PSL, send BOTH the credit card form at
     the   end   of  this  file  PLUS  the  order  form  in  the  file
     ORDERFRM.DOC.

     The Public Software Library also  maintains  a  vast  library  of
     shareware  and  public  domain  programs  and  prints  a  monthly
     magazine announcing new releases and general software news.




                    AceComm & Utilities (Tm)
                         Version  1.75
          AceComm Software Credit Card Registration Form
                    PSL Part number 10805






     Please complete this form AND the regular order form in the file
     ORDERFRM.DOC and send BOTH *** DIRECTLY *** to:

                        The Public (Software) Library
                        P.O. Box 35705
                        Houston, TX 77235-5705
                        USA


                                        Date ________________________

         Name:  _____________________________________________________

     [Company:] _____________________________________________________

      Address:  _____________________________________________________

             :  _____________________________________________________

             :  _____________________________________________________


         Payment by:   ( ) MasterCard          ( ) Visa
                       ( ) American Express    ( ) Discover Card


     Card #:  ______________________________  Exp. Date:  ___________


     Signature of card holder: ______________________________________

     PSL Part number 10805

┌──────────────────────────────────────────────────────────────┐
│            AceComm (Tm)   version 1.75   11/1/93             │
│                                                              │
│     Copyright (c) 1990-1993 by Michael G Phelps, MGP-Prog    │
├──────────────────────────────────────────────────────────────┤
│  AceComm was first released in May of 1993. The AceComm      │
│  source code is written in 100% assembly language, using     │
│  TASM versions 2, and 3.1. A Windows version of AceComm      │
│  is well under way, and should be released by March of 94.   │
│  All of the generic code written for AceComm DOS version     │
│  is available to the Windows version. This allows the two    │
│  versions to evolve together, and operate much the same.     │
│                                                              │
│  Registering AceComm gives you access to one of the more     │
│  powerful and innovative communications programs available.  │
│  AceComm registration costs just $45. (includes shipping)    │
│  Your registration package includes the printed bound user   │
│  manual, which is sure to save you back the registration     │
│  fee in on line time. AceComm's highly configurational       │
│  interface provides a progressive path to more efficient     │
│  on line sessions.                                           │
└──────────────────────────────────────────────────────────────┘
